Fatal error 5.5.3

  • Resolved meroving

    (@meroving)


    2 months ago

    Hello,
    we are still receiving error messages even after updating to 5.5.3. The whole site is up to date. Hosting: GoDaddy – if that is important.

    Could you please suggest anything to resolve this?

    Many thanks for considering my request.

    Regards, M

    Error message:


    In this case, WordPress caught an error with one of your plugins, WP Activity Log.

    First, visit your website (https://email.cloud.secureclick.net/c/7381?id=61091793.10212420.1.bdf7b0182d5941996b4f928f0a7f2b94 and check for any visible issues. Next, visit the page where the error was caught (https://email.cloud.secureclick.net/c/7381?id=61091793.11913577.1.fa6cd145799376c24f16418a6a2b80cc and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

    https://email.cloud.secureclick.net/c/7381?id=61091793.11913578.1.d286edb73817470daa0e99b1fc229b25

    To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.8.3
    Active theme: Twenty Twenty-Four (version 1.3) Current plugin: WP Activity Log (version 5.5.3) PHP version 8.3.26 Error Details

    An error of type E_ERROR was caused in line 290 of the file /dom568978/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php. Error message: Uncaught TypeError: strpos(): Argument #2 ($needle) must be of type string, false given in /dom568978/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php:290
    Stack trace: 0 /dom568978/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php(290): strpos('https://email.cloud.secureclick.net/c/7381?id=61091793.11841901.1.9fddcb489e26c4bbea8348f7c4a1248f', false) 1 /dom568978/wp-includes/class-wp-hook.php(324): WSAL\WP_Sensors_Helpers\WooCommerce_Sensor_Helper_Second::editing_product(Object(WP_Post)) 2 /dom568978/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(Object(WP_Post), Array) 3 /dom568978/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 4 /dom568978/wp-admin/edit-form-advanced.php(482): do_action('post_edit_form_…', Object(WP_Post)) 5 /dom568978/wp-admin/post.php(206): require('/dom568978/wp-a…') 6 {main}

    thrown



Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    2 months ago

    Hi there @meroving ,

    Thank you for bringing this into our attention and sorry to hear about it random occurrence; that’s actually the first time seeing anything similar.

    Could you please share a bit more information so we can investigate further?

    • The WooCommerce version you’re using.
    • The WordPress and PHP versions of your site.
    • The full error stack trace, since the one shown in the post looks truncated.
    • A short list of the plugins active when the issue occurs – for example, if you’ve managed to isolate it to WP Activity Log, WooCommerce, and a few others, please let us know which ones.
    • If possible, the exact steps to reproduce the error? This will surely be important just to have some idea how and when this occurred.
    • Last but not least, can you describe how this affects the site? Was it only a one-timer, or did it caused a plugin or site crash of any sort?

    This information will help us reproduce the issue and pinpoint what’s causing it much faster, so the more details provided, the better.

    Thanks in advance for your help in narrowing this down.

    Thread Starter meroving

    (@meroving)

    2 months ago

    Hello Lucian,

    thanks for the fast response!
    Woo: 10.3.3
    PHP: 8.3.26
    Full error – unfortunately this was the full we received in email. On Godaddy (managed WP hosting plan) we have not got the right to check the WP debug log, so I cannot tell.
    Plugins (all is up to date):

    • Check & Log Email – Easy Email Testing & Mail logging
    • CoBlocks
    • Code Snippets
    • Contact Form 7
    • Contact Form 7 Connector
    • Contact Form CFDB7
    • Extra Fees for WooCommerce
    • Google for WooCommerce
    • Pinterest for WooCommerce
    • Rank Math SEO
    • Rank Math SEO PRO
    • User Role Editor
    • USPS Checkout Fields (project custom plugin)
    • WooCommerce
    • WooCommerce Address Validation
    • WooCommerce Bulk Stock Management
    • WooCommerce Checkout Field Editor
    • WooCommerce PayPal Payments
    • WooCommerce.com Update Manager
    • Wordfence Security
    • WP Activity Log
    • WP Rocket
    • WPCode Lite
    • XPS Ship Integration
      Steps to reproduce: I could not. We just got these emails daily 1-2. Unfortunately, there is no way to one by one disable the plugins to figure out the issue because the site is live. This issue started with the previous version and then continued with the 5.3.3

    However, I understand that fixing something without the proper error message it is almost impossible. In the next 2 days I will try to retrieve the error message from the hosting company.

    Regards, M

    Thread Starter meroving

    (@meroving)

    2 months ago

    Hello @lucianwpwhite ,
    I have contacted with GoDaddy and there is no option for us to see the error log… that is just nonsense.
    Is there any way from my previous post to figure out what can be the issue here?
    Regards, M

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    1 month, 3 weeks ago

    Hello again @meroving !

    Thank you for the update!

    Unfortunately, without the full error log and detailed steps to reproduce the issue, it’s quite difficult for us to pinpoint what might be happening.

    If possible, please try to reproduce this on a staging site instead of your live environment – that will make troubleshooting safer and easier. Once you’ve isolated it there, kindly share the following details with us:

    • The exact error message or PHP log output
    • The steps that consistently trigger the error.
    • The plugins involved into this error (it would be useful if you could narrow this down by disabling some other plugins as well and only keep the ones involved)

    With that information, we’ll be able to investigate further and advise on the best next steps.

    Many thanks for your cooperation!

    Thread Starter meroving

    (@meroving)

    1 month, 3 weeks ago

    Hello @lucianwpwhite !

    Unfortunately on Godaddy on this tier this is not possible. I will try to solve this to migrate the site elsewhere for the test but it will not be fast. I guess I’ll be back with a report a few weeks later.

    Regards, M

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    1 month, 3 weeks ago

    Thank you for the follow up @meroving !

    Feel free to also reach out directly via email at [email protected] once the new details arrive (especially if they contain sensitive site info etc). This way we can exchange information easily and investigate this further 1 to 1.

    Looking forward on your updates!

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

You must be logged in to reply to this topic.