Gmail has been reset after plugin update

Hi @behindthedoors,

that’s very strange.

When did you configure our plugin with the Gmail mailer? Are you currently on the latest version: v2.5?

When you say the mailer was not configured when you logged in… What exactly do you mean by that? When you visited the plugin settings page, were the Gmail mailer settings there (Client ID and Client Secret input filled in)? Or were they empty?

Did you maybe change anything in the Google oAuth app that you were using to configure our plugin?

Take care!

The plugin updated on my website to v2.5 a couple days ago, and I just noticed that it reset on my site as well. It was set up for Gmail. Now when I go to the plugin settings, it has switched back to the default settings of Default (none). Emails are not being sent or received either. I am going to set it back up for Gmail the way it was before and turn off automatic updates.

I think I have the same problem here. Looked last night and all my previous settings seem to be back to defaults

Hey @capuderg,

Thanks for your reply!

When did you configure our plugin with the Gmail mailer? Are you currently on the latest version: v2.5?

I think around September 15th. It was working up until around that time when the 2.5 came out. And yes, we’re on 2.5.0 at the moment.

When you say the mailer was not configured when you logged in… What exactly do you mean by that?

The mailer setting was set to default PHP instead of Gmail. And the Gmail settings fields (like ClientID) were completely empty. And after testing a public contact form set up via NinjaForms, no emails have been received. That to us was the sign something’s off.

Did you maybe change anything in the Google oAuth app that you were using to configure our plugin?

Unfortunately no. No changes have been made to the Google API. I mean, if there was any, I would assume the plugin would give some sort of feedback or error about it? While what happened to us, looks like somebody literally came there and switched it back to PHP, removing all the settings for Gmail.

Getting everything back to normal was easy though: I just copy-pasted the client id and other things from the Google API pages and it seems to be working well again. But it’s just weird that it happened like that.

I hope this helps!

Hi @behindthedoors.

thank you for your info.

Everyone: @behindthedoors, @fkildoo, and @edwoodcrafting.

This is really strange… I’ve just tested an automatic update from v2.4.0 on v2.5.0 and the Gmail mailer was configured on it. After the automatic updates kicked in and updated the plugin, everything was configured as before. Mailer was set to gmail and the Client ID and secret, together with the connection was there. The test email was successfully sent as well.

I’ve also tried to find a point in the plugin that could potentially delete all plugin settings, but I could not find an obvious part of code that could do that.

Did all of you update from v2.4 to v2.5 or did someone use an older version of the plugin?

Did the plugin update for all of you via the automatic updates?

@edwoodcrafting were you using Gmail mailer as well?

Could you please also let me know which other WP plugins you are using? So I can test with other plugins and see if there is a conflict…

Thanks!

I updated from v2.4 to v2.5. It was an automated update via the Easy Updates Manager plugin. I have 23 active plugins on my site, including Easy Updates Manager, All In One WP Security, BuddyPress, Gravity Forms, Members, UpdraftPlus, and others. Those are some of the bigger plugins.

@capuderg,

Pretty sure we updated using the default plugin auto-update feature of WordPress. Not sure what was the exact version of it before 2.5, but as I said, we installed it around Sep 15 from the plugin catalog. That said, it was the version that came out before 2.5. If it was 2.4 — then that’s probably what it was.

Let me know if I can help further with investigating!

I couldn’t figure out how to get the google authorization working so I did the alternative Other and used my Gmail account. After the update, all the settings defaulted. I installed the plugin sometime back in March. bunch of plugins including WP Encryption, fast cash, force SSL

Hi everyone!

I was able to reproduce this issue and it occurs when the Gmail access token is expired (token older than 1 hour) and the automatic updates (in the background) are performed.

The root of the issue is a bug that was in v2.4 and before, however, this bug has been fixed in v2.5

When WP core is sending the “Some plugins were automatically updated” email at the end of the automatic plugin updates process, it tries to update the expired Gmail access token in our plugin settings. It looks like our plugin’s Options class is not yet updated correctly at this point for the v2.5 changes, (probably the class is cached with OPCache) and the saved plugin settings are corrupted.

So in some rare scenarios it causes the automatic updates to break our plugin settings.

We are really sorry about this issue and all the frustration it causes.

The good news is the v2.5 update has fixed the issue and future automatic updates should work as expected with no issues.

Thank you for your patience and have a nice day!

Excellent! Thank you @capuderg for investigating and for the great support.

+1 happened to me as well.
Thanks for investigating.

Thank you for looking into this, and letting us know.

What was the ultimate solution to this issue? Like others in this thread my plugin updated automatically to the 2.5 version (2.5.1), and doing so reverted my mailer setting from Gmail back to Default. I have 10 websites affected by this plugin bug, are you suggesting the SMTP has to be completely reconfigured?

Hi @dougremien,

yes, a reconfiguration is needed, but it should only be a partial configuration, not repeating the whole process of setting up the Google oAuth app.

You will have to input the Google oAuth Client ID and Secret in the plugin settings. Once you save the plugin settings and if the Refresh token is still valid the connection will be established. If the Refresh token has expired, you’ll have to complete the oAuth connection process (you’ll also probably have to add the new Redirect URI to your Google oAuth app – the new Redirect URI can be found in the plugin settings).

We are really sorry about this strange automatic updates problem and all the frustration it caused you.

Take care!