• The ImunifyAV extension is now deprecated and no longer available for installation.
    Existing ImunifyAV installations will continue operating for three months, and after that will automatically be replaced with the new Imunify extension. We recommend that you manually replace any existing ImunifyAV installations with Imunify at your earliest convenience.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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