Table Missing After V2.2.1 Update (Critical Issue)

Hi @jetxpert,

if I remember correctly, you deleted all Action Scheduler DB tables when updating to v2.1.0 of our plugin, right? Did you maybe also delete this wpmailsmtp_tasks_meta DB table?

Please check your database and see if the wpmailsmtp_tasks_meta table with your prefix exists.

If not, you could uninstall the plugin, but first, enable the “Uninstall WP Mail SMTP” checkbox in plugin settings -> “Misc” tab.

When you install the plugin again, the table should auto-generate when it’s doing the migrations.

Let me know how it goes.

Take care!

@capuderg,

Thank you, Gregor. Good memory ??

The meta table was not contained in our DB when we upgraded to V2.1.1, so nothing to delete there.

However, we will follow your instruction above and report back.

Again, thank you.

@capuderg,

Good news. We were able to reload all DB tables. However, we were successful only after accomplishing the following (procedure):

(1) Deactivated the plugin, Admin Custom Login. Your plugin (V2.1.1 and up) does not like it (and vice-versa). Admin Custom Login generates (or depends) on the following options.php entry: action_scheduler_lock_async-request-runner. Click here for details.

(2) Deactivated and deleted current (corrupted) version of WP Mail SMTP (V2.2.1). Prior to deactivation, followed your above instruction.

(3) Deleted all WooCommerce entries located inside our wp_options DB table. We don’t use WooCommmerce. They must have been added, however, by an old plugin we no longer use.

(4) Removed affected /wp-admin/options.php entries per procedure provided by Slava Abakumov (@slaffik).

(5) Installed and activated WP MAIL SMTP V2.1.1. Installing V2.2.1 first did not install all required DB tables.

(6) Updated WP MAIL SMTP to V2.2.1. Updated plugin settings.

(7) Reactivated the plugin, Admin Custom Login. Updated plugin settings.

In short, your plugin V2.1.1 (and up) — with the introduction of the actionscheduler DB tables — has caused conflicts with several other plugins (and WP Admin crashes) as reported in this forum. Once the conflict is identified, the above steps fix the issue.

Prior to V2.1.1, we NEVER had this problem. Would be great if you can provide more info as to why these new DB tables were added. Please refer us to a link or knowledge base that explains better why were they added to your plugin. Simply stating “to improve functionality” does not help us understand the downstream impact of future updates.

Update:

Item solved (using above procedure).

Cheers!

Just ran into this myself.

Can we get an update to the plugin that clears this up without going through the under the hood steps and retaining the config that is in place?

Currently running 2.5.1

@aglyons,

We are also using V2.5.1. No issues. However, as result of the Action Scheduler tables added by V2.1.1 and up, we keep getting the WP Site Health message: “The scheduled event, action_scheduler_run_queue, failed to run …”

We consider the above message a “nuisance message” at this point since we’re using a Real Cron instead of WP Cron which is what Action Scheduler works best with. The message disappears when our site is visited at the front-end over the course of the day.

In short, we are unaware of any fix or improvement beyond what was stated above. If you don’t use WooCommerce or have a Payment Portal on your website, it should be OK to use V2.1.0 if your don’t want to deal with these tables and the WP Site Health reported recommendation.

Cheers!

Hi @aglyons,

it looks like the wp_wpmailsmtp_tasks_meta DB table was not created when our plugin ran the migration for it.

Is this the only DB table that is missing for you? (The Action Scheduler tables like actions, groups, … are in your DB?)

If it’s just this wp_wpmailsmtp_tasks_meta table that’s missing, then you can try to run the migration for it again and see if it will be created this time. To trigger the migration you should change the WP Options wp_mail_smtp_migration_version from value 2, to 1. You can do that on the Options page of your WP site: /wp-admin/options.php. Make the change and click on “Save Changes”.

Then visit the plugin settings and refresh the page a few times, the DB table should create itself. If not, then something is preventing the DB table to be created and you should contact your web hosting support and ask them if they can check the DB error logs and see what is causing it.

Take care!

Hi,

If you had this issue the easiest way to fix it, it’s to create again the tablewp_wpmailsmtp_tasks_meta. To do so, just export the table from php admin from other installation, remove the content of the table in the sql file and then import the sql file in the WP where the table wp_wpmailsmtp_tasks_meta was not created correctly.

This proceedure help me a lot to fix this issue, 5 minutes and you have plugin WP Mail SMTP up and running

I hope it helps