Fatal Error 5.5.2

  • Resolved 7thcircle

    (@7thcircle)


    7 months, 1 week ago

    I get the below error when trying to access the plugin page.
    WP 6.8.3
    PHP 8.3
    Woo 10.2.2

    Uncaught Error: strpos(): Argument #1 ($haystack) must be of type string, null given
    in /var/www/sandbox.example.dev/htdocs/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php on line 899

    Call stack:

    1. strpos()
      wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php:899
    2. WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::get_plugin_dir()
      wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php:1376
    3. WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::on_available_plugin_update()
      wp-includes/class-wp-hook.php:324
    4. WP_Hook::apply_filters()
      wp-includes/class-wp-hook.php:348
    5. WP_Hook::do_action()
      wp-includes/plugin.php:517
    6. do_action()
      wp-includes/option.php:2697
    7. set_site_transient()
      wp-includes/update.php:394
    8. wp_update_plugins()
      wp-includes/class-wp-hook.php:324
    9. WP_Hook::apply_filters()
      wp-includes/class-wp-hook.php:348
    10. WP_Hook::do_action()
      wp-includes/plugin.php:517
    11. do_action()
      wp-admin/admin.php:386
    12. require_once('/var/www/sandbox.exa...s/wp-admin/admin.php')
      wp-admin/plugins.php:10
Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    7 months, 1 week ago

    Hello @7thcircle

    We’re very sorry to hear about this issue, and thank you for reporting it so quickly. Our team is already aware of this error and we’re actively working on a fix.

    In the meantime, could you please try disabling and then re-enabling the plugin to see if that resolves the error? Also, can you let me know from which version you have updated the plugin to the latest?

    It would also be very helpful if you could let us know how you performed the update : was it done normally through the Plugins page in the WordPress dashboard, or in a different way (for example, via FTP or CLI)?

    Your feedback will help us narrow down the cause and ensure this is fully addressed shortly.

    Many thanks for your patience and cooperation!

    Thread Starter 7thcircle

    (@7thcircle)

    7 months, 1 week ago

    The update was run via MainWP.

    Disabling it fixes the issue, so does rolling it back.

    If I enable it after it was disabled the issue reappears.

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    7 months ago

    Hello @7thcircle

    Thank you for your patience while we worked on this issue.

    We’ve prepared a patch that includes the fix for the problem you reported. You can find it on our Melapress Plugin Patches page here.

    To install the patch, please follow these steps:

    1. In your WordPress dashboard, navigate to Plugins → Add New → Upload Plugin.
    2. Upload the downloaded patched ZIP file
    3. When prompted, click Replace current with uploaded to overwrite your existing installation.
    4. If you previously disabled the plugin by renaming its folder, you can safely upload this version, remove the renamed one, and continue using the plugin normally.

    This fix will also be included in the next official plugin update, so once it’s released, you can safely update to the latest version through your WordPress dashboard.

    Please give the patch a try and let us know if it resolves the issue on your site.

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    7 months ago

    Hello again @7thcircle

    Thank you for your patience and cooperation while we worked on this issue.

    We’re happy to confirm that the WP Activity Log 5.5.3 update is now available, and it includes the official fix for the problem previously discussed here.

    Please go ahead and update the plugin to the latest version from your WordPress dashboard. Once updated, everything should work as expected.

    Let me know how things are going after updating, looking forward to your confirmation. Many thanks again for your understanding and for helping us get this resolved!

    Thread Starter 7thcircle

    (@7thcircle)

    7 months ago

    v5.5.3 has solved the issue. Thanks for the quick resolution as always.

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    7 months ago

    Glad to hear that @7thcircle ! Thanks for confirming this for us!

    If you want to spare one minute for us, we would appreciate if you can drop us a review based on your experience with the plugin and support; these reviews take one minute to post but they can really help out!

    Have an amazing weekend ahead!

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

The topic ‘Fatal Error 5.5.2’ is closed to new replies.