• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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