This post will maintain a list of any potential issues with updating to WP-Members 3.3.0. So far, reported issues are minor and easily fixed. While I’ll be working on smoothing out the upgrade scripts to improve the process, the following are simple corrective measures for reported issues.
Unparsed [wp-members] shortcode
Status: NOT a bug
This actually is not a bug, nor an issue with the plugin. [wp-members] as a shortcode tag was made obsolete back in versions 3.0 – 3.1. This was about 4 years ago. It was noted in the changelog and the release announcement at that time. The current 3.3.0 changelog and release notes included a list of obsolete code that underwent final removal. This included the [wp-members] shortcode tag.
Correcting this requires updating to the appropriate shortcode. See a list of replacements here.
Forms and Stylesheet Issues
If the primary “No Float” default stylesheet was used
When updating where the stylesheet selector indicates “use_custom” but the actual URL is to a default stylesheet. The problem can be corrected manually, but this fix applies the custom URL to the new standard setting for the defaults.
Status: Fixed in 3.3.0.1
Any other stylesheet (other than “No Float” default)
This was due to the database version being wiped when settings were updated. This fix correctly applies the database version when updating settings.
Status: Fixed in 3.3.0.1
Error on New Registration
There was an issue with the various captchas the plugin supports due to a couple of factors. First, the captcha class dependency was not loaded at all times that it was needed. Second, the validation function needed to be handled as a static class and was not.
Status: Fixed in 3.3.0.1
User Profile Not Displaying Fields
It was intended to introduce separate selection of fields for registration and profile update in 3.3.0. However, there is an issue that causes profile fields to both (1) not correctly display and (2) if they do, they do not update correctly.
Status: Fixed in 3.3.0.2
[wpmem_logged_in /] shortcode “meta_key” attribute
There was a logic flaw in some of the new feature code for the meta key attribute in the wpmem_logged_in shortcode.
Status: Fixed in 3.3.0.3
Rollback
If necessary, 3.3.0 can be rolled back to the previous version. If you are experiencing any issues that do not yet have a fix, you can roll back by removing the 3.3.0 version of the plugin and installing a previous version.
IMPORTANT: DO NOT run the “delete” option from the WordPress plugin panel when doing a rollback. That will delete all of your current plugin settings and require you to update your settings.
Rollback is best handled via FTP.
- Go to the plugin’s “advanced” page in the wordpress.org repository.
- At the bottom of that page, select the version you need to roll back to.
- In the WP plugin panel, deactivate WP members.
- Using FTP, delete the contents of the wp-members folder (/wp-content/plugins/wp-members).
- Unzip the roll back version locally.
- Using FTP, copy the roll back version to your site.
- Reactivate.
