I am getting ready for the WP-Members 2.8.3 release. This version is focused on completing some of the user table features that were not completed in 2.8.2. This includes the addition of screening the users (showing not active, not exported, etc) as well as patching some a couple of bugs from 2.8.2 that didn’t pass custom columns.
There are also some fixes and some new features in this release.
- Allows native fields display_name, nicename, and nickname to be removed from the field manager. Previously, these native WP fields could be added, but since they were marked as native fields and native fields cannot be removed, if you made a mistake, you were kind of stuck having to delete all your field settings and start over. Now you can delete these fields.
- New filter wpmem_logout_link filters all logout links. This filter makes it a little easier to filter the logout links. Before, you could filter the dialog. But if you wanted to change just the link, you needed to write a filter function that would extract the link (which could be dynamic in some places) and replace it. Now you can just do the link by itself if that’s all that is needed.
- Added default registration via wp-login page (backend). This of course can be disabled by unchecking “anyone can register” in the WP settings. I have found on more than one occasion a user has marked the plugin as “broken” or worse, given it a one star rating because they didn’t read the simple directions about how the plugin puts registration on the front end. For those users who refuse to read directions (and thus will not be reading this as you are), I’ve added a feature that will put the custom registration fields you add via the field manager to the native backend WP registration screen (wp-login.php). If you follow the recommended setting of unchecking “anyone can register” that will disable this and you’ll have just the front-end features as usual. Please note that as with any new feature, there may be potential issues in some configurations – if you think you found a bug in this, please let me know.
- Completion of user admin panel implementation. Added screens for non-active and non-exported users. This takes us a step closer to fully deprecating the Users > WP-Members page, since all of its features are now available in Users > All Users. If all goes well with this release, we will deprecate Users > WP-Members in the next version.
- Added a custom column to page/post tables to indicate if a post/page is blocked/unblocked opposite the chosen default setting. Lots of users have asked for this – and because I use the plugin myself, I have found that it really is needed. If you have a mix of blocked and unblocked content in your posts or pages, it is difficult to determine if a given post or page is different from the default setting. This new feature will indicate only the posts and pages that are opposite the default you have set in the plugin’s options. For example, if you have posts set to be blocked by default, this column in your posts table will indicate only if a post is unblocked.
- Fixed bug in admin/post.php that caused an error due a typo in the selected capability. This bug was only a factor when running WP in debug mode (which you shouldn’t be doing on a production site anyway).
- Applied the patch for the users table custom columns that didn’t return non-WP-Members custom column values.
- Fixed the use of the nonce constant to check if the constant is defined.
- Applied patch to the utilities file that left some debugging code artifacts in the 2.8.2 release.