Support » Plugin: Relevanssi - A Better Search » Relevansi Throws an Error

  • Hi guys,

    Just messing around updating a few pages on my website this morning, and (just the) one of these pages kept on saying that there was a critical error.

    Checked in my email, and it said that it was due to Relevanssi.

    I deactivated Relevassi whilst I updated my page, then re-activated it, and it all works fine now.

    Any chance of working out where the problem is – remember WordPress has just updated to 5.7?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Mikko Saari

    (@msaari)

    We’ve tested with 5.7 and no issues have been found. Can you please tell me the exact error message you got? That would help a lot and without the specific error I can’t do much.

    Thread Starter deeveearr

    (@deeveearr)

    Hi @msaari

    the error message reads:

    There has been a critical error on this website. Please check your site admin email inbox for instructions.

    Learn more about troubleshooting WordPress.

    On a relevanssi deactivation , it just updates normally.

    Plugin Author Mikko Saari

    (@msaari)

    That is not the error message. That’s just information that there has been an error message, and unfortunately not helpful at all. Your admin email should have the actual error message, or if you haven’t received any email, look in the server PHP error log. I need the specific PHP error message, otherwise I can’t really even begin to know what the problem is.

    Thread Starter deeveearr

    (@deeveearr)

    Yes, I just deleted the email about 5 minutes ago, so I tried updating the page again to try and get another one, and it went straight through.

    Sorry, it must be gremlins.

    Plugin Author Mikko Saari

    (@msaari)

    If you do see the error again, I’m very interested, I just need the error message in order to fix things.

    Thread Starter deeveearr

    (@deeveearr)

    Will do – I just updated the page five times, but it won’t go wrong now…

    Thread Starter deeveearr

    (@deeveearr)

    Hang on, I just found the email in my trash bin:

    Error Details
    =============
    An error of type E_ERROR was caused in line 707 of the file /home/midland6/public_html/wp-content/plugins/relevanssi/lib/utils.php. Error message: Uncaught TypeError: Argument 1 passed to relevanssi_strip_all_tags() must be of the type string, null given, called in /home/midland6/public_html/wp-content/plugins/relevanssi/lib/indexing.php on line 1520 and defined in /home/midland6/public_html/wp-content/plugins/relevanssi/lib/utils.php:707
    Stack trace:
    #0 /home/midland6/public_html/wp-content/plugins/relevanssi/lib/indexing.php(1520): relevanssi_strip_all_tags(NULL)
    #1 /home/midland6/public_html/wp-content/plugins/relevanssi/lib/indexing.php(574): relevanssi_index_content(Array, Object(WP_Post), '3', false)
    #2 /home/midland6/public_html/wp-content/plugins/relevanssi/lib/indexing.php(805): relevanssi_index_doc(13497, true, Array, true)
    #3 /home/midland6/public_html/wp-content/plugins/relevanssi/lib/indexing.php(873): relevanssi_publish(13497, true)
    #4 /home/midland6/public_html/wp-includes/class-wp-hook.php(294): relevanssi_insert_edit(13497)
    #5 /home/midland6/public_html/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
    #6 /home/mid
    Plugin Author Mikko Saari

    (@msaari)

    The error was caused because the post content is for some reason null. Not even empty, but completely void of anything. Any idea why? This was about post 13497, is there something unusual about that post? What kind of content does it have?

    Thread Starter deeveearr

    (@deeveearr)

    Well actually, the page is one of four different pages containing a ‘Feedzy’ feed, so there is content, plus a title for the feed on it – but none of the other three pages threw that error message.

    I reckon that Relevanssi just drew the poisoned chalice when WordPress was deciding where it’s error messages came from.

    • This reply was modified 7 months, 2 weeks ago by deeveearr.

    Similar issue here. Today’s update to the plugin broke our site. Have disabled it for now and everything is running fine again. Feedback from our hosting tech support:

    There is an issue with your ajax requests, the server is spamming your /wp-admin/admin-ajax.php which is overloading the server.

    Here is a quick view of the logs:

    69.162.173.119 – – [10/Mar/2021:10:41:18 -0600] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 32 “https://www.ultimationinc.com/wp-admin/admin-ajax.php” “WordPress/5.7; https://www.ultimationinc.com”
    69.162.173.119 – – [10/Mar/2021:10:41:18 -0600] “POST /wp-admin/admin-ajax.php HTTP/1.1” 499 0 “https://www.ultimationinc.com/wp-admin/admin-ajax.php” “WordPress/5.7; https://www.ultimationinc.com”
    69.162.173.119 – – [10/Mar/2021:10:41:18 -0600] “POST /wp-admin/admin-ajax.php HTTP/1.1” 499 0 “https://www.ultimationinc.com/wp-admin/admin-ajax.php” “WordPress/5.7; https://www.ultimationinc.com”
    69.162.173.119 – – [10/Mar/2021:10:41:18 -0600] “POST /wp-admin/admin-ajax.php HTTP/1.1” 200 32 “https://www.ultimationinc.com/wp-admin/admin-ajax.php” “WordPress/5.7;

    Plugin Author Mikko Saari

    (@msaari)

    @rcanny Yours is a completely different problem. Please start a new thread for it and please provide more context. Did everything work well with 4.12.3? Do you have any more information on what’s causing these ajax requests? Just regular searches? Doing something in admin? Please provide more information in a new thread.

    Today’s update didn’t change anything about admin-ajax (except in Premium, but if you’re on Premium, please use the Premium support at https://www.relevanssi.com/support/).

    Yes, I am on premium. I will start a new thread there. I am not a developer only the customer. Everything worked fine until we updated the plugin. Then the updated plugin broke the site. Then the hosting company disabled the plugin and the site worked again. They told me to raise a ticket with you, so I did.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Relevansi Throws an Error’ is closed to new replies.