• I get a recurrent error triggered by DataAccess.php line 253 (PHP Type:  E_ERROR).

    Example output of the stacktrace error array:

    Array (
    [type] => 1
    [message] => Uncaught Error: Object of class WP_Error could not be converted to string in /home/example/public_html/wp-content/plugins/404-solution/includes/DataAccess.php:253 Stack trace: #0 /home/example/public_html/wp-content/plugins/404-solution/includes/DataAccess.php(504): ABJ_404_Solution_DataAccess->queryAndGetResults('\n/* -----------...') #1 /home/example/public_html/wp-content/plugins/404-solution/includes/SpellChecker.php(440): ABJ_404_Solution_DataAccess->storeSpellingPermalinksToCache('2010/10/\xC2\xBFtacos...', Array) #2 /home/example/public_html/wp-content/plugins/404-solution/includes/SpellChecker.php(313): ABJ_404_Solution_SpellChecker->findMatchingPosts('2010/10/\xC2\xBFtacos...', '1', '1') #3 /home/example/public_html/wp-content/plugins/404-solution/includes/WordPress_Connector.php(274): ABJ_404_Solution_SpellChecker->getPermalinkUsingSpelling('2010/10/\xC2\xBFtacos...') #4 /home/example/public_html/wp-content/plugins/404-solution/404-solution.php(162): ABJ_404_Solution_WordPress_Connector->process404() #5 /home/example/public_html/wp-includes/class-wp-hook.php(324): abj404_404listener('') #6 /home/example/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #7 /home/example/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #8 /home/example/public_html/wp-includes/template-loader.php(13): do_action('template_redire...') #9 /home/example/public_html/wp-blog-header.php(19): require_once('/home/example/...') #10 /home/example/public_html/index.php(17): require('/home/example/...') #11 {main} thrown
    [file] => /home/example/public_html/wp-content/plugins/404-solution/includes/DataAccess.php
    [line] => 253 )

    I’ve seen this error in several different sites. The error occurs when a request is made to view some removed pages/files but not all of them. I think it has something to do with special characters used in URL slugs upsetting the spellchecker in 404 Solution.

    Have you seen the error before and is there a fix?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Aaron

    (@aaron13100)

    Are you on the latest version?

    I’ve made a small change to the code that might give us more information about the error in version 2.36.7 (if the line in the log applies to version 2.36.6).

    Anyway please update to 2.36.7 and if possible activate the “Help the developer by sending error logs” option where the issue happens. If all goes well then there should be an error, but a different log message and we might see the actual cause of the issue.

    thanks

    Aaron

    Thread Starter Lee Hodson (VR51)

    (@leehodson)

    Thank you, Aaron.

    I’ve updated the plugin to 2.36.7 and enabled Help a Developer in the settings.

    I won’t specify the site’s name here. The site is entirely PG. You will know the error log is from me because it will contain the first word ‘mama’ with two words initialled L & T spelled all-in-one; and it is a Latina site.

    I receive a report for each error. If you need to see the full report that lands in my inbox I could send it to you if I knew where to send it (I could find the addy if you wanted me to). Let me know.

    Lee

    Plugin Author Aaron

    (@aaron13100)

    I replied to your email. You can send me the error logs whenever you like, or paste the to https://pastebin.com/ and give me the link here (the logs are too long to paste here directly).

    Thread Starter Lee Hodson (VR51)

    (@leehodson)

    Thank you, Aaron. I replied to your email.

    When I receive an error report triggered by the new version of 404 Solution I will send you a copy of that error report too.

    Plugin Author Aaron

    (@aaron13100)

    Both issues should be fixed in 2.36.9. Let me know how it goes.

    Thread Starter Lee Hodson (VR51)

    (@leehodson)

    I’ve not had any error reports sent to my inbox since the new version was installed. I think it is safe to say the issue is resolved.

    Thank you so much for your help, Aaron.

    I’ve marked this thread as resolved.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Error Caught in DataAccess.php’ is closed to new replies.