• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

wp-cron.php is there a missing parameter in cronjob?

Iolomot

New Pleskian
Server operating system version
Almalinux 8.10
Plesk version and microupdate number
18.0.67
Howdy I noticed that the cronjob created by Plesk to replace the default Wordpress one does not have the "doing_wp_cron" parameter.
Why?
Shouldn't it run /wp-cron.php?doing_wp_cron in this case?


capture.png
 
Howdy I noticed that the cronjob created by Plesk to replace the default Wordpress one does not have the "doing_wp_cron" parameter.
Why?
Shouldn't it run /wp-cron.php?doing_wp_cron in this case?

The doing_wp_cron parameter is only used in conjunction with the ALTERNATE_WP_CRON option. Plesk doesn't use the ALTERNATE_WP_CRON option, rather it disables the build-in WP cron all together with the DISABLE_WP_CRON option and instead calls the wp-cron.php page directly via a scheduled task (cron job). Which is, in most cases, the most reliable and efficient way the handle the WP cron.
 
The doing_wp_cron parameter is only used in conjunction with the ALTERNATE_WP_CRON option. Plesk doesn't use the ALTERNATE_WP_CRON option, rather it disables the build-in WP cron all together with the DISABLE_WP_CRON option and instead calls the wp-cron.php page directly via a scheduled task (cron job). Which is, in most cases, the most reliable and efficient way the handle the WP cron.
Thanks
 
Back
Top