Fatal error: Uncaught Error: Class “FS_Admin_Notices”

  • Resolved pennink

    (@pennink)


    1 year, 11 months ago

    Here’s the stack trace:

    Fatal error: Uncaught Error: Class "FS_Admin_Notices" not found in /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/classes/Settings.php:1825 Stack trace: #0 /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/classes/Migration/class-migration.php(126): WSAL_Settings->set_mainwp_child_stealth_mode() #1 /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/classes/Migration/class-migration.php(541): WSAL\Utils\Migration::migrate_up_to_4420() #2 /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/classes/Migration/class-abstract-migration.php(164): WSAL\Utils\Migration::migrate_up_to_4421() #3 /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php(1245): WSAL\Utils\Abstract_Migration::migrate() #4 /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php(409): WpSecurityAuditLog->update() #5 /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/wp-security-audit-log.php(1207): WpSecurityAuditLog->setup() #6 /home/sites/2a/1/18b1ee8e02/public_html/wp-includes/class-wp-hook.php(308): WpSecurityAuditLog->install('') #7 /home/sites/2a/1/18b1ee8e02/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array) #8 /home/sites/2a/1/18b1ee8e02/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #9 /home/sites/2a/1/18b1ee8e02/public_html/wp-admin/plugins.php(194): do_action('activate_wp-sec...') #10 {main} thrown in /home/sites/2a/1/18b1ee8e02/public_html/wp-content/plugins/wp-security-audit-log/classes/Settings.php on line 1825

    This is occurring on at least 3 different sites right now.

Viewing 15 replies - 1 through 15 (of 19 total)

  • I have the same issue. All of my sites on WPEngine are having this issue.

    Same here. A lot of my websites were down and I needed to remove the plugin via SFTP to get them up again.

    Plugin Support robertabela

    (@robert681)

    Hello @matthiaspabst @7thcircle @pennink

    Can you please confirm if this error is showing up on websites on which there is the MainWP Child site plugin installed as well?

    Thanks.

    @robert681 Confirmed! MainWP Child is running on theses sites.

    Thread Starter pennink

    (@pennink)

    Yes, it is happening on 3 sites with the Main WP Child plugin. However, those are just 3 out of some 50-odd sites with both plugins installed. Only the 3 are generating the fatal error.

    Plugin Support robertabela

    (@robert681)

    Thanks for the updates. We are looking into this right now. We’ll keep you posted.

    Plugin Support robertabela

    (@robert681)

    Hello @pennink @matthiaspabst @7thcircle

    We have a patch ready for you. We have tested it but we would appreciate if you can test it yourself as well at least on one of the websites on which you are encountering the issue.

    Please download the patch “20221209_wp-activity-log-mainwp-patch” from our support page.

    Please let us know how the testing goes.

    Thread Starter pennink

    (@pennink)

    We have uploaded the patch to the 3 sites where the fatal error was occurring. We had previously deactivated the plugin and were unable to reactivate it due to the fatal error. Now with the patch version, we are able to successfully reactivate the plugin with no fatal error.

    Plugin Support robertabela

    (@robert681)

    I am glad to hear that @pennink

    Thanks for reporting back. I’ll wait for the other two to report back as well. Thanks a lot for the speedy response.

    @robert681 two infos:

    1. The patched version 4.4.3.1 works!

    2. The “buggy” version 4.4.3 also works, when the plugin is not hidden from the plugins list. I just found out, that on all problematic sites the option was set to “Yes, hide the plugin and any WP Activity Log plugin extensions from the list of installed plugins”. Though I can’t remember that I set this option to this value (makes no sense on sites where I’m the only user).

    Plugin Support robertabela

    (@robert681)

    Thank you very much for the detailed feedback @matthiaspabst

    The plugin has a “Stealth / silent mode” which is activated when it is installed alongside a MainWP child site plugin. Could it be that in these cases you have installed the plugin after installing the MainWP child site plugin?

    @robert681 Yes! That must have been the case. Yesterday I deleted the version 4.4.3 via SFTP and re-installed the version 4.4.2.1 by uploading the ZIP file at /wp-admin/plugin-install.php.

    Good to know about this automatic stealth mode feature on sites already running MainWP Child!

    The patch works for me. All impacted sites are running MainWP Child and the activity log was initially installed after MainWP. All sites are also running in stealth mode.

    Where can we find a copy of the patched version please I’m still getting a fatal error when installing the WP Activity Log Version 4.4.3 from WordPress Plugin installation.

    Thanks

    Plugin Support robertabela

    (@robert681)

    Hello @clu55ter

    Please download the patch “20221209_wp-activity-log-mainwp-patch” from our plugins patches download page.

    This should do the trick. Please let us know if you need anything else from our end.

    Have a great week ahead.

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Fatal error: Uncaught Error: Class “FS_Admin_Notices”’ is closed to new replies.