@passegua @rostymatviyiv
We’ve compiled some additional steps that (are similar to those above). Can you try these out and see if they help with this issue?
https://aioseo.com/docs/troubleshooting-action-scheduler-issues/
My host provider wrote me this:
(automatic translation from Italian)
the mysql database Sql1345755 appears to be in MySql Version: 5.7 and WordPress is set to use DB_CHARSET latin1_swedish_ci within the database. Please check the compatibility of these features with the All in One SEO plugin.
benjaminprojas
(@benjaminprojas)
9 hours, 18 minutes ago
@passegua @rostymatviyiv
We’ve compiled some additional steps that (are similar to those above). Can you try these out and see if they help with this issue?
https://aioseo.com/docs/troubleshooting-action-scheduler-issues/
As soon as I activate the Action Scheduler plugin my web site crashes, so it’s impossible continue. I had to deactivate and remove Action Scheduler plugin.
Versione di WordPress 5.6
Tema corrente: Twenty Twelve (versione 3.3)
Plugin corrente: Action Scheduler (versione 3.1.6)
Versione PHP 7.4.10
Dettagli dell’errore
====================
Un errore di E_ERROR è stato causato nella linea 44 del file /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/action-scheduler-3.1.6/classes/migration/ActionScheduler_DBStoreMigrator.php. Messaggio di errore: Uncaught RuntimeException: Error saving action: Error saving action: Table ‘Sql1345755_4.wp_actionscheduler_actions’ doesn’t exist in /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/action-scheduler-3.1.6/classes/migration/ActionScheduler_DBStoreMigrator.php:44
Stack trace:
#0 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/action-scheduler-3.1.6/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action()
#1 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/action-scheduler-3.1.6/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action()
#2 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/action-scheduler-3.1.6/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store()
#3 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/action-scheduler-3.1.6/functions.php(36): ActionScheduler_ActionFactory->single()
#4 /web/htdocs/www.sinapsi.org/home/wordpr
Updated to version 4.0.10 still CRASH
deactivated.
SEO for WordPress. Features like XML Sitemaps, SEO for custom post types, SEO for blogs, business sites, ecommerce sites, and much more. More than 65 million downloads since 2007.
Versione 4.0.10 | Di: All in One SEO Team | Visualizza i dettagli
Questo plugin non è stato caricato correttamente e viene messo in pausa durante la modalità di ripristino.
Un errore di E_ERROR è stato causato nella linea 44 del file /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php. Messaggio di errore: Uncaught RuntimeException: Error saving action: Error saving action: Table ‘Sql1345755_4.wp_actionscheduler_actions’ doesn’t exist in /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44 Stack trace: #0 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action() #1 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action() #2 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/plugins/all-in-one-seo-pack/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store() #3 /web/htdocs/www.sinapsi.org/home/wordpress/wp-content/
@passegua,
Did you ever hear back from folks from the Code Snippets plugin? What about your hosting provider?
The issue here is that the tables we require for AIOSEO to work are not being created. Either your database is preventing that from happening, or you have something in your options table that is preventing it from working.
Let us know when you hear back from either your hosting provider or the code snippets authors and we can go from there.
Did you ever hear back from folks from the Code Snippets plugin? What about your hosting provider?
I am still waiting a solution from my host provider, this is holiday season…
The issue here is that the tables we require for AIOSEO to work are not being created. Either your database is preventing that from happening, or you have something in your options table that is preventing it from working.
I wrote this to my host provider…
Let us know when you hear back from either your hosting provider or the code snippets authors and we can go from there.
Sure, hopefully this will be fixed.
Mean while I am reading many users struggling with this woocommerce table problem.
@passegua @benjaminprojas I’ve just fixed that issue.. it is actually related to your hoster or your wordpress setup itself and not to the plugin.
You just need to make sure that your database user has proper permissions to “CREATE” new tables in database.
So I had this issue on PRODUCTION, but all was working properly locally, the reason was that I was using root locally which could do anything in database, however on PROD the user had limited permissions, without “CREATE” permission. I’ve simply added those permissions and it helped.
https://jmp.sh/eUMMiDW
@passegua @benjaminprojas I’ve just fixed that issue.. it is actually related to your hoster or your wordpress setup itself and not to the plugin.
You just need to make sure that your database user has proper permissions to “CREATE” new tables in database.
So I had this issue on PRODUCTION, but all was working properly locally, the reason was that I was using root locally which could do anything in database, however on PROD the user had limited permissions, without “CREATE” permission. I’ve simply added those permissions and it helped.
https://jmp.sh/eUMMiDW
Hi rostymatviyiv.
I do not understand where did you take that screenshot from?
Thanks.
however on PROD the user had limited permissions, without “CREATE” permission. I’ve simply added those permissions and it helped.
Please explain me better what do you mean. What PROD is?
Thanks
@passegua just send that information to your hoster, I guess they will understand what should be done.
PROD is PRODUCTION environment, installation of your website that is world wide available for other users. Beside that you can have more installations for different purposes and available only for limited amount of people (for developers, for customer, for QA department and so on)
@passegua Hello. I was struggling with this error for a few days also.
@rostymatviyiv is right.
I have changed the rights of the database user : you have to be sure that the user can “CREATE” and not only “READ” “WRITE” etc.
Then I deactivated the plugin which caused problems.
Then I ran the plugin Fix Action Scheduler Action IDs :
https://gist.github.com/rrennick/165225412aca1a4fc04f05898cb97101
It created the tables.
Then I Activiated AIOSEO again! –> OK!
Thank you @rostymatviyiv !
@passegua for info it has nothing to do with the WordPress admin panel.
It depends on the hosting company.
Generally, you can find this setting inside the “admin center” or “manager” of the hosting company (where you can manage DNS, php versions and… databases)
I hope it will help.
Good news!
Eventually my host provider support solved the issue.
It was a mysql db charset problem.
They manually changed the charset and manually created the tables.
I hope this solution could be useful to other users.
Please have a look at the screenshot.
-
This reply was modified 5 years, 5 months ago by
passegua.
Hey @passegua,
I am SO glad to hear your hosting provider was able to fix this for you. Do you know what the charset it was originally set to? That info would definitely be helpful going forward.
Also @jullxb, thank you for chiming in and helping us out.
We really appreciate you both for helping us work through this issue.
– Arnaud
