After automatic updates – error message

Hi, i’d got the nearly same problem today! *
But the recovery mode of WP to login didn’t work for me.
So i deactivated Security Ninja (Version 5.214) via ftp. Will look to find the previous version …
or i’ll wait for the next update 🙂

Fehler-Details ============== Ein Fehler vom Typ E_ERROR wurde in der Zeile 294 der Datei /homepages/39/d4297111480/htdocs/le/wp-content/plugins/security-ninja/includes/class-wf-sn-utils.php verursacht. Fehlermeldung: Uncaught Error: Class "WPSecurityNinja\Plugin\wf_sn_el_modules" not found in /homepages/39/d4297111480/htdocs/le/wp-content/plugins/security-ninja/includes/class-wf-sn-utils.php:294 Stack trace: #0 /homepages/39/d4297111480/htdocs/le/wp-includes/class-wp-hook.php(324): WPSecurityNinja\Plugin\Utils::secnin_fs_license_key_migration() #1 /homepages/39/d4297111480/htdocs/le/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /homepages/39/d4297111480/htdocs/le/wp-includes/plugin.php(517): WP_Hook->do_action() #3 /homepages/39/d4297111480/htdocs/le/wp-admin/admin.php(175): do_action() #4 /homepages/39/d4297111480/htdocs/le/wp-admin/index.php(10): require_once('/homepages/39/d...') #5 {main} thrown

WordPress-Version 6.6.2 Aktives Theme: CHILD of „Responsive“ Version: 6.0.0 Aktuelles Plugin: Security Ninja (Version 5.214) PHP-Version 8.1.29

• This reply was modified 8 hours, 16 minutes ago by aundc.

I have noticed the same misbehavior since at least version 5.213.

Aktives Theme: Divi Theme (version 4.27.1) Aktuelles Plugin: Security Ninja (Version 5.214) PHP-Version 8.2.23

“What does this error code mean and what do I have to do to get everything running smoothly again?”

For quick fix rename the Plugin to another Name and reload the Dashboard. Until a fix is available.

Facing the same issue after auto update from 5.213 to 5.214. Recovery mode also not working.

• This reply was modified 4 hours, 3 minutes ago by TechMan.

Hello everyone,

Thank you all for bringing this issue to our attention. I sincerely apologize for the trouble you’ve encountered after updating to version 5.214. We’ve identified the cause of the problem and have just released version 5.215, which includes a fix for this specific error and other related issues.

Additionally, we have removed the recommendation for auto-updates as we understand this can sometimes lead to unexpected issues, and we want to ensure everyone has more control over when updates are applied.

Please update to version 5.215, and let us know if you continue to experience any issues. We’re deeply sorry for the confusion and hassle this has caused, and we’re here to help if you need further assistance!