• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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