Hannah West Design

Hi Gregor! I don’t think you got much sleep since we last spoke.

I reloaded the page and it did exactly what you said it would. That admin notice disappeared and the new one just says “The next queue will begin processing in approximately 57 seconds.” There is a table now with one action, “wp_mail_smtp_admin_notifications_update.” I can now see the db table, xxx_actionscheduler_actions.

That should mean I’m safe to apply the update now, right?

Aha! Here’s the admin notice: “It appears one or more database tables were missing. Attempting to re-create the missing table(s).”

I also see that an update (2.4.0) is available. I usually apply those as soon as I see them but I’m waiting on this one until I hear from you.

I’m guessing that your next thing is going to be to suggest that I go ahead and follow the directions to install/restore the tables as instructed on your website: How to Troubleshoot Action Scheduler Issues (WP Mail SMTP 2.1.1)

Hi Gregor, I’m using version 2.3.1. The value of action_scheduler_migration_status is COMPLETE.

Well, I went for the option to restore from the backup. I did have to redo some settings in the form and SMTP plugin, but that only took a minute, and the main thing is that it worked! Test emails sent form the contact form reached their destination. The odd thing is that there are still only three action_scheduler db tables, no actionscheduler_actions. Will that cause issues in the long run?

I was so scared that the site would go down when I went to install and activate the SMTP plugin that I had the Plugins folder open in the hosting account so I could rename it quickly in case it did, but all went smoothly. Maybe the other plugin corrupted the data in one of those tables?

The last table I’m not sure about is wpyw_wpforms_tasks_meta
(Known plugins that use this table name: wpforms-lite [not installed]). I have to admit that I’m afraid to remove it, but really it’s only 4.4Kb in the database so I might just leave it in place.

Thank so much for your help and for answering my final questions.

Hi again Gregor, before I try your solution I wanted to run something by you. Just before the fires made me pack up my computer last week I deleted BOTH plugins. The database now contains these actionscheduler tables: xxx_actionscheduler_claims, xxx_actionscheduler_groups, and xxx_actionscheduler_logs. I’m not sure but I think I remember there being four of these before all this started. I’m wondering if I should restore the site from aback taken before I installed the first SMTP helper plugin and then try installing yours, effectively bypassing any effect the other one might have had on the database.
And if for some reason that fails, then I can fall back to the solution at the link you posted. Thoughts?

Apologies for the late reply. Southern Oregon had a terrible wildfire last week and I had to keep my computer packed up for possible evacuation until yesterday. The plugin that did this was Post SMTP Mailer/Email Log. Thanks for the link to recreate the db tables, I’ll try that tomorrow.

I contacted our host and despite replacing WP core files, updating PHP and bumping memory limits, after deleting both plugins, then optimizing the database and reinstalling your plugin, which worked for us initially, whatever damage has been done by the other plugin causes yours to crash the site when activated now. I am going to hunt down a new plugin, and if I can’t find one I’m not sure what I can do to get her email working. I’m really disappointed in what has happened.

I contacted our host and despite replacing WP core files, updating PHP and bumping memory limits, after deleting both plugins, then optimizing the database and reinstalling the WP Mail SMTP plugin that worked for us initially, whatever damage has been done causes the plugin to crash the site when activated now. I am going to hunt down a new plugin, and if I can’t find one, I guess I’ll see if yours can help with our new Gmail setup, but I’m really disappointed in what has happened.

Just discovered the same error on its sister website, light-path-resources.org. There is a third site I manage for the same client, militarytruth.org, which is also connected to the same Jetpack account and it does not have the same issue.

Oh, I see. It’s under Manage, not Tools. I went through the steps you suggested just now and then checked a post to see the comment form. It still has the error. When Jetpack is deactivated, the comment form returns to normal.

• This reply was modified 4 years, 6 months ago by Hannah West Design. Reason: added more info

I’m sorry, but I’m not seeing the path you specified: My Site ->Tools ->Settings ->Security. I’m not sure how to include a screenshot here to show you what I do see. But after scrounging around through all the “cupboards,” I do not see anything about security (privacy, yes, but that doesn’t include the settings you mention) anywhere in this site’s menu/settings.

I was referring to being logged in to the admin account on the website. Now that I have tried when logged in to the site’s Jetpack-related WordPress account and then my own WordPress account, the issue remains if I am logged in to the website. If I log out of the website, the comment form displays as expected whether I’m logged in to the site’s WordPress account or my own.

Hm, more info. Now that a little bit of time has passed since I checked on the site and wrote my last post, I needed to do something on it and checked a post to see what the status of the comment form was, and it was fine! In a regular browser window, not logged in…and as soon as I did log in, the error reappeared. Just FYI in case it’s helpful.

Hi @kokkieh, thanks so much for responding! I was still seeing the error when reading your email, however, the comment form displayed as expected after loading the site in an incognito window, both when I was logged out and after I logged back in. I did not need to delete any cookies or do any of the other steps you mentioned. How do you interpret this behavior now?

• This reply was modified 4 years, 6 months ago by Hannah West Design. Reason: Added 2nd to last sentence

Thanks, Asad. Doing that now.