Hi David,
Thanks for reaching out to us.
Yes, you can manually run the migration from here- WooCommerce > Status > Tools > “Variation Swatches for WooCommerce” Migrator
If that doesn’t help, please make a staging copy of your site using this plugin- https://wordpress.org/plugins/wp-staging/
Then give us access to your staging to identify your issue.
For your production site-
Here is the tutorial on how you can rollback the Free version to 2.0.31: https://www.loom.com/share/2d8bc9351e864e1d964e319e27564250
Please download the 2.0.31 pro version of Variation Swatches For WooCommerce from here: https://drive.google.com/file/d/1PnNEO7C3KxzIfeo46yOiX0NZQLQN1kqv/view?usp=sharing
Then manually add it to your site.
Thank You
Update Migration Failed – Swatches misassigned
David Tattersall
Hi,
We updated manually the Pro version of this plugin yesterday. Briefly all of the swatches disappeared, then after we reactived the newly updated pro plugin. Some kind of migration scheduled action started and some of the swatches slowly started coming back.
This migration then failed when it hit the 300 second PHP timeout limit. (Which is already pretty high)
Now it has left loads of swatches abandoned and misassigned to the wrong variations and/or colours all over the site.
We have a backup of before this migration but being an eCommerce site it’s not as simple as just reverting due to the loss of orders and customer information. There is of course also no guarantee that this migration won’t just fail again.
Is there anyway to get this migration to finish and/or continue or start again?
This is the error in action scheduler
woo_variation_swatches_pro_run_migrate Failed
‘callback’ => ‘woo_variation_swatches_pro_migrate_210_products_swatches_settings’ woo-variation-swatches-pro-migration Non-repeating 2024-06-10 11:38:27 +0000 (19 minutes 14 seconds ago)
2024-06-10 11:38:26 +0000 action created 2024-06-10 11:38:41 +0000 action started via WP Cron 2024-06-10 11:44:37 +0000 action marked as failed after 300 seconds. An unknown error occurred. Check server, PHP, and database error logs to diagnose the cause.