App for Cloudflare® Pro 1.9.2

[grafwebcuso]

The stack trace shows the error is triggered by "cfPurgeCache" which suggests a plugin related to caching or Cloudflare is the issue.

Any idea?

 

[grafwebcuso]

It is effecting a plugin we use to upload and then delete data on a website. Entry Automation from Cosmic Giant

 

[digitalpoint]

Do you have the stack trace itself?

 

[grafwebcuso]

I have checked the currently pending crons using WP-CLI and there were quite a few. You can review the attached text document for information.

Trying to run all events that are due now, results in the following error:

=======================================
root@204-12-99-132:/home/########/public_html# wp cron event run --due-now --allow-root
Executed the cron event 'wsal_summary_weekly_report' in 0.557s.
Executed the cron event 'wsal_periodic_reports_weekly' in 0.003s.
Executed the cron event 'wordfence_email_activity_report' in 0.341s.
Fatal error: Uncaught Error: Unknown named parameter $urls in /home/nvbjorbnvbiuebri/public_html/wp-includes/class-wp-hook.php:324
Stack trace:
#0 /home/######/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#1 /home/#######/public_html/wp-includes/plugin.php(565): WP_Hook->do_action(Array)
#2 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(358): do_action_ref_array('cfPurgeCache', Array)
#3 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(238): Cron_Event_Command::run_event(Object(stdClass))
#4 [internal function]: Cron_Event_Command->run(Array, Array)
#5 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func(Array, Array, Array)
#6 [internal function]: WP_CLI\Dispatcher\CommandFactory::{closure:WP_CLI\Dispatcher\CommandFactory::create_subcommand():97}(Array, Array)
#7 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(497): call_user_func(Object(Closure), Array, Array)
#8 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(441): WP_CLI\Dispatcher\Subcommand->invoke(Array, Array, Array)
#9 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(464): WP_CLI\Runner->run_command(Array, Array)
#10 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1316): WP_CLI\Runner->run_command_and_exit()
#11 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#12 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(83): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
#13 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(32): WP_CLI\bootstrap()
#14 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('/usr/local/cpan...')
#15 /usr/local/cpanel/3rdparty/wp-toolkit/plib/vendor/wp-cli/wpt-wp-cli.php(31): require_once('/usr/local/cpan...')
#16 /usr/local/bin/wp(4): require_once('/usr/local/cpan...')
#17 {main}
thrown in /home/############i/public_html/wp-includes/class-wp-hook.php on line 324
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
root@204-12-99-132:/home/n#########/public_html#
=======================================

It is very likely that it is related to the PHP version used or a specific plugin/theme is causing a conflict, so I would recommend that you troubleshoot this further with your developer.

 

[digitalpoint]

I can't think of a situation where a cron task would schedule URLs to be purged, but then not include any URLs. That being said, I added an extra check for the next version that should (hopefully) prevent the cron task from being scheduled if WordPress doesn't know the URL of the post (for whatever reason).

In the meantime, you can clear existing cron task with WP-CLI...

List existing cron tasks:

wp cron event list

Delete cron task:

wp cron event delete cfPurgeCache