• Resolved x1code

    (@secretja)


    025/10/22 15:27:14 [error] 21351#21351: *162876 FastCGI sent in stderr: "PHP message: PHP Warning: Undefined property: stdClass::$plugin in /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php on line 1374PHP message: PHP Fatal error: Uncaught TypeError: strpos(): Argument #1 ($haystack) must be of type string, null given in /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php:899
    Stack trace:
    #0 /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php(899): strpos(NULL, '/')
    #1 /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php(1376): WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::get_plugin_dir(NULL)
    #2 /www/domain/public/wp-includes/class-wp-hook.php(324): WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::on_available_plugin_update('update_plugins', Object(stdClass), 0)
    #3 /www/domain/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
    #4 /www/domain/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hello @secretja

    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 x1code

    (@secretja)

    Hi Lucian,

    I did that and the outcome is the same, same error, renamed plugin folder, renamed back and activate, the same. I’m not 100% sure but I think I updated it from Version 1.15.0. I updated in bulk with other plugins via Dashboard -> Updates.

    Thread Starter x1code

    (@secretja)

    Sorry, wrong version 5.5.1 to 5.5.2.

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Thank you for all the details provided so far, @secretja!

    We’ve identified the cause of the error and have already prepared a preliminary fix. We’re now waiting on a few confirmations to ensure everything is stable. If all goes well, this fix will be included in an upcoming maintenance update very soon, so please stay tuned.

    We really appreciate your patience and cooperation while we work through this.

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hello again @secretja !

    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)

    Hello again @secretja !

    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 x1code

    (@secretja)

    Hi Lucia,

    Thank you! Update on all websites and all works fine. Thank you one more time.

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Thank you for your confirmation @secretja ! Glad to hear that!

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

You must be logged in to reply to this topic.