WP-Members 3.5.0 was released a couple of days ago. There have been a few reported issues, most of which are not severe, but could be annoying. All of them will be fixed ASAP and a bug fix release will be pushed out. In the meantime, here is a list of the known issues and the quick fix for each if needed.
Full package of bug fixes
There are currently 5 known bugs in WP-Members 3.5.0. They are all listed below. (If you discover a bug that is not listed below, then it may be unknown. Please let me know.)
There will be a full production release with all of these fixes soon. In the meantime, the plugin has been packaged with these fixes and you can download it from github here:
https://github.com/rocketgeek/wp-members-dev/releases/tag/3.5.0.1
You can also go to the following link on wordpress.org, and from the section titled “Advanced Options”, select the “development version” (which is 3.5.1, which will be released into production later this week)
https://wordpress.org/plugins/wp-members/advanced/
If you wish to apply just a single fix for any of these, each item listed below includes a link to the necessary patch file.
Admin notification email [fields] shortcode
There’s an issue in the wpmem_fields() function that doesn’t return the fields for the admin notification. The patched version included in the gists resolves this.
Replace wp-members/includes/class-wp-members-forms.php with the patched version.
Fatal error on WP-CLI (or in autoupdates)
This issue results in a warning similar to the one below:
PHP Warning: require_once([…]/wp-content/plugins/wp-members/includes/cli/class-db-tools.php): Failed to open stream: No such file or directory in […]/wp-content/plugins/wp-members/includes/class-wp-members.php on line 817
The cause is a misnamed file in the production package. A quick fix is to just rename the class-wp-members-cli-db-tools.php file to class-db-tools.php. Or, a patch file is provided that includes the correctly named file. If you rename the file, it’s OK – the next update will overwrite everything it needs to.
Replace wp-members/includes/class-wp-members.php with the patched version.
PHP error when updating shortcode settings in shortcodes tab.
When updating the settings for the [[wpmem_fields]] shortcode in the Shortcodes tab, this results in the following error (or similar):
Fatal error: Uncaught Error: Cannot use object of type WP_Members_Shortcodes as array
in [...]/wp-content/plugins/wp-members/includes/admin/tabs/class-wp-members-admin-tab-shortcodes.php on line 138
3.5.0 adds a new “Shortcodes” tab for dealing with shortcode settings. Currently, the only setting is for the shortcode. This setting was part of some early security patches in 3.4.9.x and it was placed on the main options screen primarily to get it out the door quickly. But now that there has been some time to improve the interface, the new tab was added. Unfortunately, 3.5.0 has a bug in this screen so that when you update the setting, it throws a PHP fatal error (a halt of code execution) because it treats an object as an array. Note that your setting is actually saved – the error is thrown when the screen is redrawn. So if you refresh, you’ll see the screen again and the saved setting. But… that’s not ideal, so this patch fixes that. It will be included in the next release, but if you can’t wait, apply the patch file.
Replace wp-members/includes/admin/tabs/class-wp-members-admin-tab-shortcodes.php with the patched version.
Password reset link results in an invalid link
This issue is a localized issue that depends on your specific webserver, PHP, and WordPress configurations, but there is a fix for it.
Replace wp-members/includes/class-wp-members-pwd-reset.php with the patched version.
Double input display on field edit for certain field types
The bug is that in the edit view of a select, multiselect, multicheckbox, or radio field, there are two textarea inputs. This is due to an oversight when developing some improvements to how the add/edit screens worked with regards to these four field types.
Replace wp-members/includes/admin/tabs/class-wp-members-admin-tab-fields.php with the patched version.
Fields not added to native registration form and/or not processed from Add New screen
This bug causes WP-Members fields to not be added to the native WP registration form and not processed in the Users > Add New screen (even though they are added there).
This requires changes to more than one file, so there is no recommended patch file. It is fixed in the full release package that can be downloaded from github (listed at the top of this post).