Hi Oliver,
Thanks for the report. I’ve opened a Github issue here:
https://github.com/Automattic/jetpack/issues/30382
I’ll mark this forum thread as resolved. Please follow that Github thread for updates on the issue! Thanks 🙂
Thank you. I’ve subscribed to the Github thread.
Oliver
@domainsupport the WP Cron event job jetpack_v2_heartbeat can be removed with Advanced DB Cleaner PRO. I was actually checking if it was ok to delete the cronjob jetpack_v2_heartbeat if Jetpack was uninstalled, and found your thread. Removing it now.
Thanks!
@nikkoboy Yes, you can use Crontrol plugin too. We actually developed a maintenance plugin that detects CRON events with no associated actions with an option to delete them.
WP Crontrol and Advanced DB Cleaner Pro both don’t fix this problem: The cron jobs reappear instantly – So much for your commercial plugs
@strompf If you are seeing the CRON jobs re-appear then you still have the plugin active. This support topic is about the CRON jobs not being removed when the plugin is deactivated which is different to your issue.
Apologies for my unfriendly tone of voice. I don’t think I can remove my previous posting. On a hopefully more constructive tone:
- I don’t have Jetpack installed
- I’ve tried to remove the cron jobs
jetpack_clean_nonces
and jetpack_v2_heartbeat
in various ways, including through SQL, the helper plugin from Automattic, their PHP code for the same purpose and various WP-CLI approaches, including using wp option patch delete cron <ids>
to surgically remove the entries from wp_options » cron
, but within a second, these two jobs appear again, with a new (higher) id
- However, this only happens when WooCommerce is active, so I suspect that WooCommerce somehow recreates these jobs, eventhough
DISABLE_WP_CRON
has been set to true
- And yes: Those two plugins do delete such cron jobs – It’s not their fault that WooCommerce somehow seems to recreate them. My apologies again.
Help is still appreciated 😉
-
This reply was modified 1 year, 3 months ago by
strompf.
Hi @strompf –
Since you don’t have Jetpack installed and this happens when WooCommerce is active, please post on the WooCommerce forums:
The WooCommerce team should be able to help investigate what is happening here.