-
Notifications
You must be signed in to change notification settings - Fork 814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cron job 'jetpack_v2_heartbeat' not removed after Jetpack is deactivated #30382
Comments
Yes, that's something we could add to the uninstall routine for sure, or / and to the disconnection method: jetpack/projects/packages/connection/src/class-manager.php Lines 2000 to 2007 in 210e753
cc @Automattic/jetpack-kernel, who may have more ideas there. |
Somewhat related:
It may be nice to do an audit of what needs to happen when Jetpack is deactivated when other Jetpack plugins are still vs. not, and ensure that we only leave what's necessary based on the situation. |
I have also 2 cron jobs that I can not delete, although I deinstalled the plugin and cleaned the database: jetpack_clean_nonces |
I have the same issue, two cron jobs still active after Jetpack was uninstalled: jetpack_clean_nonces Update: It looks like they're both present in WooCommerce. e.g. 'jetpack_v2_heartbeat' is identified in Does anyone know it can be safely removed? |
I will take care of this. |
Impacted plugin
Jetpack
Quick summary
A Jetpack user in the forums has reported that the cron job
jetpack_v2_heartbeat
is not removed after deactivation: https://wordpress.org/support/topic/wp-cron-jetpack_v2_heartbeat-not-being-removed/Can y'all confirm whether this needs to be added to the list of things that are removed upon plugin deactivation/deletion (or if it already is included and there's perhaps something else going on here?)
Thanks!
The text was updated successfully, but these errors were encountered: