class-itsec-scheduler-cron.php:3 Fatal Error

  • maumar

    (@maumar)


    5 years, 10 months ago

    I got in my access_log:
    [Mon Jun 22 18:42:18.979349 2020] [proxy_fcgi:error] [pid 21927] [client 172.68.198.125:28852] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Cannot unset string offsets in /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/lib/class-itsec-scheduler-cron.php:466\nStack trace:\n#0 /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/modules/global/settings.php(108): ITSEC_Scheduler_Cron->uninstall()\n#1 /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/modules/global/settings.php(73): ITSEC_Global_Settings_New->handle_scheduler_change()\n#2 /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/modules/global/settings.php(56): ITSEC_Global_Settings_New->handle_cron_change()\n#3 /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/lib/settings.php(87): ITSEC_Global_Settings_New->handle_settings_changes()\n#4 /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/lib/settings.php(60): ITSEC_Settings->set_all()\n#5 /var/www/clients/client1/web3/web/wp-content…’, referer: https://www.xxxxx.it/wp-admin/

    [Mon Jun 22 19:27:01.252674 2020] [proxy_fcgi:error] [pid 27801] [client 172.68.198.125:46774] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Class ‘ITSEC_Scheduler’ not found in /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/lib/class-itsec-scheduler-cron.php:3\nStack trace:\n#0 {main}\n thrown in /var/www/clients/client1/web3/web/wp-content/plugins/better-wp-security/core/lib/class-itsec-scheduler-cron.php on line 3′

    Debian 10
    PHP 7.4.7 (cli) (built: Jun 12 2020 07:47:45) ( NTS )

    • This topic was modified 5 years, 10 months ago by maumar.
    • This topic was modified 5 years, 10 months ago by maumar.
Viewing 1 replies (of 1 total)
  • nlpro

    (@nlpro)

    5 years, 10 months ago

    The first one seems to be a bug in the uninstall() method in the better-wp-security/core/lib/class-itsec-scheduler-cron.php file.

    The iTSec plugin makes use of 2 possible schedulers for scheduling events. The (WP) cron scheduler (default and preferred) or the page-load scheduler (fallback in case WP Cron is unavailable).

    Due to a bug (and under certain specific circumstances) the iTSec plugin will automatically switch from the cron scheduler to the page-load scheduler. Specifically (test) sites that run the risk of not receiving any requests for a time period of 24 hours tend to make that (undesired) switch.

    When the iTSec plugin scheduler switches from cron to page-load one of the things that need to happen is that the currently scheduled iTSec cron events are purged. Due to a bug in the uninstall() method of the cron scheduler the purge fails.

    The second error is probably a domino effect.

    If you are interested we can enable an extra Debug page which may assist you in getting the (WP) cron scheduler up and running again. Additionally we can add a constant to the wp-config.php file that will force the iTSec plugin to use the cron scheduler (and not switch back to the page-load scheduler).

    To prevent any confusion, I’m not iThemes.

Viewing 1 replies (of 1 total)

The topic ‘class-itsec-scheduler-cron.php:3 Fatal Error’ is closed to new replies.