Latest update broke Woocommerce
-
Updating woocomerce this morning has caused a complete failure of WordPress install. all other plugins and theme were updated, Error shows as :
RuntimeException thrown Error saving action: Error saving action: Database error.
had to remove woocommerce to get the site running again. re-installing Woocommerce causes the site to crash again.
-
This topic was modified 5 years, 9 months ago by
thedrelle.
The page I need help with: [log in to see the link]
-
This topic was modified 5 years, 9 months ago by
-
Howdy!
I’ve seen the error most recently associated with outdated versions of PHP.
Can you make sure your PHP version is at least
7.2+?If the version of PHP is not up to date, the document at this link can help with the update process, or contact your hosting provider for help.
after the update off wordpress the woocommerce plugin once i activate i got this error
An error of type E_ERROR was caused in line 44 of the file /home2/iugyyymy/public_html/wp-content/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php. Error message: Uncaught RuntimeException: Error saving action: Error saving action: Table ‘iugyyymy_WPRGS.YQD_actionscheduler_actions’ doesn’t exist in /home2/iugyyymy/public_html/wp-content/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44
Stack trace:
#0 /home2/iugyyymy/public_html/wp-content/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL)
#1 /home2/iugyyymy/public_html/wp-content/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action))
#2 /home2/iugyyymy/public_html/wp-content/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store(Object(ActionScheduler_Action))
#3 /home2/iugyyymy/public_html/wp-content/wp-cYo tambien actualizar WordPress y luego salir ya ERROR
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON dataHey Zach.
I am running PHP 7.3
What else could be the issue? it seems to be a database issue, but I have no clue what.
-
This reply was modified 5 years, 9 months ago by
thedrelle.
@amoraplatanado @ezzmokhtar please create your own threads here in the forums so everyone can get help individually one their specific issues.
@thedrelle is there more to that error message about the database? There’s normally a bit more telling exactly what database table it’s referring to, and what it was trying to do.
that is the odd thing, I am seeing no PHP errors relating to the page. It looks like the update may have failed, and I never caught the error relating to that when it happened. as I cannot get into the woocommerce settings, i can’t look at and error log there, and don’t see that one was generated in the directory.
I have reinstalled woocommerce on the site right now so you can see what exactly the site does when it is installed.
I have reinstalled woocommerce on the site right now so you can see what exactly the site does when it is installed.
Just had a look and I see WooCommerce is now deactivated on the site again.
What is the process and error steps when you try updating and activating WooCommerce? Is the
RuntimeException thrown Error saving action: Error saving action: Database errornotice the only thing you see, or does it look like WooCommerce gets removed from the Plugins section and doesn’t display there, etc?The more information we can gather about the issue, the better it will help us with finding the cause. Thanks!
sorry, The site only shows that error. let me reinstall woocommerce and set that up for you right now.
I just tried removing EVERYTHING EXCEPT the woocommerce plugin.
got this in the debug.log
[25-Aug-2020 15:05:15 UTC] PHP Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “read_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /home/bi-admin/public_html/wp-includes/functions.php on line 5225
[25-Aug-2020 15:05:15 UTC] PHP Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “read_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /home/bi-admin/public_html/wp-includes/functions.php on line 5225
[25-Aug-2020 15:05:15 UTC] PHP Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “read_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /home/bi-admin/public_html/wp-includes/functions.php on line 5225
[25-Aug-2020 15:05:15 UTC] PHP Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “edit_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /home/bi-admin/public_html/wp-includes/functions.php on line 5225
[25-Aug-2020 15:05:15 UTC] PHP Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “edit_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /home/bi-admin/public_html/wp-includes/functions.php on line 5225
[25-Aug-2020 15:05:15 UTC] PHP Notice: map_meta_cap was called incorrectly. The post type shop_order is not registered, so it may not be reliable to check the capability “edit_post” against a post of that type. Please see Debugging in WordPress for more information. (This message was added in version 4.4.0.) in /home/bi-admin/public_html/wp-includes/functions.php on line 5225
[25-Aug-2020 15:06:46 UTC] PHP Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: Database error. in /home/bi-admin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44
Stack trace:
#0 /home/bi-admin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL)
#1 /home/bi-admin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action))
#2 /home/bi-admin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store(Object(ActionScheduler_Action))
#3 /home/bi-admin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/functions.php(36): ActionScheduler_ActionFactory->single in /home/bi-admin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44
[25-Aug-2020 15:06:46 UTC] PHP Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: Database error. in /home/bi-admin/public_html/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44Thanks for that info @thedrelle!
It looks like this should be able to be solved by the info here:
https://github.com/woocommerce/action-scheduler/issues/587#issuecomment-658168773
I’d recommend asking your hosting provider to help with that.
Figured that out, and ran as instructed.
Failed to execute SQL : SQL CREATE TABLE
wp_actionscheduler_actions(action_idbigint(20) unsigned NOT NULL AUTO_INCREMENT,hookvarchar(191) COLLATE utf8mb4_unicode_520_ci NOT NULL,statusvarchar(20) COLLATE utf8mb4_unicode_520_ci NOT NULL,scheduled_date_gmtdatetime DEFAULT NULL,scheduled_date_localdatetime DEFAULT NULL,argsvarchar(191) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL,schedulelongtext COLLATE utf8mb4_unicode_520_ci,group_idbigint(20) unsigned NOT NULL DEFAULT ‘0’,attemptsint(11) NOT NULL DEFAULT ‘0’,last_attempt_gmtdatetime DEFAULT NULL,last_attempt_localdatetime DEFAULT NULL,claim_idbigint(20) unsigned NOT NULL DEFAULT ‘0’,extended_argsvarchar(8000) COLLATE utf8mb4_unicode_520_ci DEFAULT NULL, PRIMARY KEY (action_id), KEYhook(hook), KEYstatus(status), KEYscheduled_date_gmt(scheduled_date_gmt), KEYargs(args), KEYgroup_id(group_id), KEYlast_attempt_gmt(last_attempt_gmt), KEYclaim_id(claim_id) ) CHARACTER SET latin1 COLLATE latin1_swedish_ci; failed : Table ‘wp_actionscheduler_actions’ already existsIs it possible that this has something to do with the charset in wp-config is set to utf-8?
-
This reply was modified 5 years, 9 months ago by
thedrelle.
After doing more digging, it looks like this issue looks to actually be caused by WordPress itself:
* https://github.com/woocommerce/woocommerce/issues/25709
* https://github.com/woocommerce/woocommerce/issues/25744It look like the only recourse may be a clean install.
please confirm, and thank you for your time.
Yes, I would definitely try a clean install as that should resolve the issue.
Let us know how that goes!
-
This reply was modified 5 years, 9 months ago by
The topic ‘Latest update broke Woocommerce’ is closed to new replies.