WP-Members 3.4.4 is primarily a maintenance release. It incorporates a series of minor changes since 3.4.3 along with some additional code improvements for performance and fixing some minor issues.
Changes and improvements when enabling memberships
This version adds excerpts for membership restricted content when the user is logged in but does not have the required membership. It should work the same as excerpts when the user is not logged in.
In addition to this, the excerpt itself is added to the wpmem_product_restricted_args filter.
A [memberships] shortcode was added for use in the admin notification email. You can add this to the admin notification and it will list the memberships assigned to the user.
The plugin now only loads membership/product restriction if the setting is active. So if you disable memberships, but have a membership requirement on a post/page, it will revert to the standard logged in requirement without additional steps necessary to remove membership restriction.
The password reset process of emailing a link to the user has undergone some code improvements since 3.4.3. There was a long-standing issue in certain situations where the WP function for
the_content() may be run more than once on a page and that created a problem for the password reset because the code logic was completed as part of the
That logic process has been moved to be handled by an earlier WP action (specifically
template_redirect) and as of 3.4.4, the [wpmem_profile] and [wpmem_form password] shortcodes do not rely on the
the_content filter at all, even to display the messaging.
If you have not converted your setup to use the new password reset link, keep in mind that the old process of resetting a password and emailing it to the user will be completely obsolete in version 3.5.0. If you use the legacy password reset, make sure you have changed over before then.
This version fixes a potential issue in the [wpmem_field] shortcode that would throw an error if the field did not have a defined field type. Generally, this is not an issue if the field is created through the Fields tab in the plugin admin, but in situations where a custom field is created by filtering
wpmem_fields, if the type is not defined, there could be an error. So the shortcode was improved to allow for an undefined field type.
The export user object class was moved into the main plugin files. This is primarily a change in the directory structure with no change in the plugin function, as the export API function was already changed previously to be useable in the front end when called. This is just a file move, but it’s important if you use any customization that may have called to directly load the file. You shouldn’t do it that way because the object class is loaded when the API function
wpmem_export_users() is used. If you do have a customization that calls the file directly from the admin files, then it is recommended that you remove that call altogether.
The admin object load has been moved back to WP’s
init action for legacy support of some of the plugin’s premium extensions.
Plugin dependencies in the plugin’s main object class has been moved to load after settings are loaded, not before.