Prevent the Action Scheduler 3.0 migration from running in WooCommerce 4.0 on child sites.
Snippet Type
Execute on Child Sites
Snippet
add_filter( 'action_scheduler_migration_dependencies_met', '__return_false' );
2 Likes
Hi Sebastian,
It would be helpful if you provided some context here. Why would MainWP users want to prevent the Action Scheduler 3.0 migration from running on child sites? Thanks!
1 Like
I was going to ask the same question because if you block this process, what is the impact on WC store? Thanks @phillcoxon for the question!
It would be if you have a lot of data related to the Action Scheduler on your store and wanted to run the data migration to AS 3.0.x using WP-CLI.
It would not cause any issues in WooCommerce since AS data storage usage is abstracted for how it stores data.
More info can be found here.
1 Like
The Action Scheduler is already merged into WooCommerce core but an older version is currently being used. For WooCommerce 4.0 release version 3.0.x of the Action Scheduler will be included.
1 Like
More info about the upcoming WooCommerce 4.0 release next month.
2 Likes
Whaouuu! Impressive @sebastian-moran - Are you a WooCommerce expert? Thank you for all the explanation. Looks like we are not using those functionalities…
I know a few things about WooCommerce.
2 Likes