Home of WP-Members, The Original WordPress Membership Plugin
Chad Butler · ·
This article will discuss some elements of the login form that sometimes confuse users (and admins). Some of these concepts are not necessarily specific to WP-Members (or even WordPress) while some are, and some overlap. Continue Reading →
Chad Butler · ·
WP-Members 3.3 is now in official development. You can keep up with the development process via the Development Repository on Github.
Version 3.3 will bring some important changes that have been pending for awhile. There have been some pending features that both I and members of the user community have wanted to see brought into the plugin and some of these may break past functionality. I usually try to keep things very backward compatible, so I figured that if we are going to “upset the apple cart,” then it’s probably best to do as much of it all at the same time, so users only have to do a major site audit one time. Continue Reading →
Chad Butler · ·
The WP-Members User List is getting a much needed major rebuild. This will result in the 2.0.0 version, bringing it up-to-date with the other 2.0 series extensions. It will be more object oriented and includes some new features. Continue Reading →
Chad Butler · ·
WP-Members 3.2.6 is a security release with some additional updates. Because this includes a security update, it is recommended that you take steps to update from previous versions.
Here is an overview of what is included in this update:
There is a potential exploit with regard to the password change. It’s a limited exploit, but I feel any potential risk no matter how small needs to be addressed and closed. In this case, the fix is twofold and completely closes the discovered exploit and goes beyond that requirement. The function for password change can only be fired if the user is logged in. Additionally, a nonce has been added to the plugin’s short form (used for login, password change, password reset, and forgot username forms). Nonces were made a default of the long form in the previous version (it was previously optional). So this version adds that to the short form.
Some of the functions in the plugin’s API were updated and improved.
The logic for the function behind the [wpmem_field] had a ground-up rebuild. This will make the function more efficient and also easier to maintain in the future as new features are added. (Note: While this is not a “feature,” it is noted here so that if you experience any unexpected behavior in the [wpmem_field] shortcode following the upgrade, please let me know about it so it can be determined if it is related to the update.)
The registration form field validation was updated to evaluate required fields as “not null” instead of false/empty. This allows for “0” values which would previously have been evaluated as “false” and thus lead to the form returning an empty required field error if a “0” was entered. Since the current logic has been in place for almost 10 years, I’m surprised this hasn’t actually come up before, but with the addition of support for the HTML number field type, I did have a user indicate that they needed their number field to accept a minimum value of “0” – so now you can do that.
Added file post ID to the post_data array. The post_data array is passed through various filters and actions during the registration process. In the case of a file field type (“file” or “image”), this array of data now includes the post ID for the attachment. While this can be used for various things, the primary reason for inclusion was being able to easily find a file uploaded during registration for attachment to an email (i.e. sent as an attachment to the admin notification). While that could previously be done without this addition, the change makes it much simpler and eliminates any setup steps – the post ID needed is included in the data array.
WP-Members relies on WP’s wp_mail() function to send email. It’s important to understand a few things about wp_mail():
If you want to send HTML formatted email, you need to change the content type.
The plugin includes a setting in the Emails tab to automatically send emails as HTML format. (NOTE: When sending HTML formatted email, URLs are not “automatically” made clickable. You need to apply proper HTML markup for links and any other formatted text.)
Use the wp_mail_content_type filter to set the content type to “text/html”:
add_filter( 'wp_mail_content_type', 'my_set_mail_content_type' );
function my_set_mail_content_type( $content_type ) {
return 'text/html';
}The wpmem_email_headers filter allows you to filter the email headers. Use that to set the email type as “text/html”:
add_filter( 'wpmem_email_headers', 'my_wpmem_html_email' );
function my_wpmem_html_email() {
return "Content-Type: text/html" . "\r\n";
}Adding one of above filter function to your functions.php file or a custom plugin file will allow you to send HTML formatted emails. Now you can use HTML in the email content in the plugin’s email management tab (be sure to include appropriate shortcodes for data being sent). There is more information on how to use code snippets from this site here.
Ready to get started?