WP Member update to 3.0.0.1 took down site on v.4.2.2

Interesting that it would run fine on the dev and not on the live. Is it possible there are differences between that two systems?

My first inclination is to suggest downloading the zip and uploading it via FTP for the update. Sometimes, especially on busy days (such as today when an update is being heavily downloaded) the transfer process through the WP admin panel is not always a clean one. So direct upload is a way to make sure all components are correctly updated.

When doing this, make sure to deactivate the plugin, delete existing files (maintain a backup), upload the new files, then reactivate the plugin.

Because the messages you are getting indicate the new settings for the plugin were not saved, make sure you also go to the plugin’s main options tab and save settings.

The messages you have in the shot there are “notices” and not errors. This means either you have WP running in debug mode or php set to display all/strict messaging. Neither of these are ideal for a production site.

Many thanks, Chad. You were spot on. I did a manual install and all went well. Odd I got a clean install on the dev. site through the dashboard and not on the production site. But I’m good to go. Thanks for your rapid response.

No problem – glad to hear you got a clean install the second go.

Also, just to check – I released 3.0.0.2 a few minutes ago. If you use the login shortcode or reCAPTCHA, you’ll want to make sure you’re on that version.

Got that first go around. Again, a bow of gratitude!

No problem!