The WP-Members 3.1.9 release should clean up some loose ends before the next major update (where there will be some settings changes and some other feature changes). There are not any major changes in 3.1.9 that would prevent rolling back to a previous version.
Here’s an overview of the changes in this release.
Improved User Search
Version 3.1.9 has an additional set of options to vastly improve the user search via the Users > All Users screen. You will notice a new column in the Fields tab – “Users Search”. This column allows you to choose custom fields to be added as available searchable fields.
WP’s user search on the Users > All Users screen is by default limited to essentially the username and the user’s email address. That’s a very limited set of options and can be bothersome if you have a lot of users and want to search for a user by their real name, or perhaps by an address element such as city.
Now you can choose what fields are included in the search, which should make searching for users a lot simpler now.
reCAPTCHA Version 1 Obsolete
Google stopped supporting reCAPTCHA version 1 a long time ago. While v1 was unavailable for new WP-Members installs, I had worked it so that users could leave this to their own update schedule.
Now with PHP 7.1 compatibilities to consider, I had to remove version 1 support completely. The v1 code library is incompatible with PHP 7.1 and causes errors when used. Since WP-Members itself is compatible with PHP 7.x, this issue makes it appear as if it is not.
Any installs with reCAPTCHA version 1 selected will now load version 2.
Other Deprecated and Obsolete Elements
There are some other legacy elements in the plugin that are obsolete and are being handled in this release. This includes the comments_template.php file in the (former) /lib/ directory. This file was previously used to load an empty “dummy” comments template for blocked content. But that process hasn’t been used for quite some time and the entire process is handled by filter functions in the main object class. So this obsolete file is being removed.
There are a number of functions being deprecated in this release. Most of them are part of the dashboard profile display and update. This version introduces an entirely new process for the dashboard (WP admin) profile display and update functions and essentially merges what was previously two separate processes. There had been one set for non-admins and one set for admins. With the addition of adding multipart form support, this became cumbersome, so I rebuilt the entire process to be handled singularly. The old functions are moved to deprecation (see the readme file for details).
This release has a number of other updates, including the following:
- Set image fields to display the “medium” thumbnail in the dashboard by default (previously loaded full size).
- Image fields in the admin profile link to the media editor for the file.
- Added a default format for date field shortcode to match the date format setting in the WP options.
- Added a “format” attribute for the date field shortcode to allow custom format.
Fixes in this release:
- Removed the “height” property of the button_div wrapper in the generic stylesheets. Depending on the size of the login button inherited by a given theme, this height could end up smaller than the button causing the button to bleed into the links area. Removing the “height” should correct this and make the stylesheets more broadly compatible without adjustment.
- Removed the $requested_redirect_to argument used by the login_redirect filter hook in the login process. This was causing some compatibility issues and unintended behaviors when used with the Advanced Options extension.
- Fixed the [wpmem_form user_edit] shortcode to display updated user data without a page refresh.
- Fixed the [wpmem_form password] shortcode and the password change process of the [wpmem_profile] shortcode to maintain the user’s login state when the password is changed.
- Added corrective processing for select (dropdown), multiple select, multiple checkbox, and radio fields if the value pairs have a comma after the final value. Previously, having a comma after the final pair caused some PHP warnings, but this is fixed in this release.
- Fields tab bulk action previously only checked the action. Fixed this to check the page and the action to avoid namespace collisions with other plugins.