Fatal Error updating 2.0.1 to 2.1.1 on WP Multisite

  • Resolved fab

    (@fabloool)


    3 years, 10 months ago

    Updating 2.0.1 to 2.1.1 on WP Multisite and PHP 7.2 i have got the following Error:

    
Fatal error: Uncaught RuntimeException: Error saving action: Error saving action: Table 'squisitodev.wp_actionscheduler_actions' doesn't exist in /var/www/html/squisitodev.com/public/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44 Stack trace: #0 /var/www/html/squisitodev.com/public/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action(Object(ActionScheduler_Action), NULL) #1 /var/www/html/squisitodev.com/public/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action(Object(ActionScheduler_Action)) #2 /var/www/html/squisitodev.com/public/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store(Object(ActionScheduler_Action)) #3 /var/www/ht in /var/www/html/squisitodev.com/public/wp-content/plugins/wp-mail-smtp/vendor/woocommerce/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44
    • This topic was modified 3 years, 10 months ago by fab.
    • This topic was modified 3 years, 10 months ago by Yui. Reason: please use CODE button for code formatting
Viewing 8 replies - 1 through 8 (of 8 total)
  • Sanjeev Aryal

    (@sanzeeb3)

    3 years, 10 months ago

    Hi @fabloool,

    I’m sorry you ran into issues with this update! Version 2.1.1 added the Action Scheduler library, which adds really valuable flexibility for current and future development. But unfortunately, we’ve seen that some sites run into unexpected issues with setting up the datatables needed to let Action Scheduler work.

    From what we’ve been able to see so far, this typically seems to be a result of server configuration issues. We’ve been doing everything we can to sort out what those specific configuration issues are and how to overcome them.

    Using everything we know about these issues so far, and how to resolve them, we’ve published a step by step doc: https://wpmailsmtp.com/docs/how-to-troubleshoot-action-scheduler-issues-wp-mail-smtp-2-1-1/.

    I hope that’s helpful!

    Sanjeev Aryal

    (@sanzeeb3)

    3 years, 9 months ago

    Hi @fabloool – We haven’t heard from you in about a week, so I’m going to go ahead and mark this ticket resolved. If you still have questions, though, please feel welcome to continue the conversation.

    Albert Calzada

    (@calzbert)

    3 years, 6 months ago

    hello
    i have the same error, but i can’t resolve it with your doc.
    any idea?

    Sanjeev Aryal

    (@sanzeeb3)

    3 years, 6 months ago

    Hi @calzbert,

    Is the error message you’re getting exactly the same? Could you please share full error logs and let me know if you’re also on multisite? You might want to check out the steps outlined in this thread. That will help to recreate the database tables required.

    Thanks!

    Albert Calzada

    (@calzbert)

    3 years, 6 months ago

    Hi!
    yes. i’m using multisite.
    I use multilingualpress to clon one site to other.

    i try steps of you thread.
    it works parcially.
    i can “active” wp mail stmp on second site without break WordPress.
    on the principal subsite, wp mail smtp works fine

    but in second site, we have problem withs databeses.
    i try your thread and it works very well. i can active plugin. but i have now this alert about _wpmailsmtp_tasks_meta.

    any idea?
    thanks!

    Plugin Author Gregor Capuder

    (@capuderg)

    3 years, 6 months ago

    Hi Albert,

    it looks like when you cloned the site it did not create the needed DB tables for this new site.

    Probably other DB tables are missing as well, but for the _wpmailsmtp_tasks_meta, you can find this WP option: wp_mail_smtp_migration_version and change the value from 2, to 1. This will run the second migration, which should create the _wpmailsmtp_tasks_meta table. You can visit: .../wp-admin/options.php of your new site, search for wp_mail_smtp_migration_version, change the value from 2, to 1 and then save changes.

    Let me know if that will resolve your issue.

    Take care!

    Albert Calzada

    (@calzbert)

    3 years, 6 months ago

    Hi!
    yes, it works perfectly.

    thank you very much

    Plugin Author Gregor Capuder

    (@capuderg)

    3 years, 6 months ago

    Hi Albert,

    that’s great! 🙂

    Have a nice day!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Fatal Error updating 2.0.1 to 2.1.1 on WP Multisite’ is closed to new replies.