RocketGeek

Home of WP-Members, The Original WordPress Membership Plugin

Home » Archives for bug-fix

bug-fix

WP-Members 3.1

· ·

This article is provided free. Find out how you can get full access to premium content, including how-to articles and support forums, as well as priority email support and member exclusive plugin extensions..

 

WP-Members 3.1 contains some long awaited features, some fixes, and some improvements.

There are no changes to the database with this update so if you are currently at 3.0 or higher, you should be able to roll back without difficulty.  (If you are using a version earlier than 3.0, there are changes from 2.x to 3.x that will be implemented in this update that would affect rolling back to 2.x.  If that’s the case for you, you should test the update on a development system prior to upgrading.)

This version is currently available on GitHub as version 3.0.10.  There will be no official 3.0.10 release on wordpress.org – this is merely a transitional release tag for building and testing leading into the official 3.1.0 release.  The 3.0.10 is packaged and available for testing.  The full production release of 3.1.0 will be available soon.

Here is a list of new features, improvements, and fixes: Continue Reading →

WP-Members 2.9.8 Release

· ·

This article is provided free. Find out how you can get full access to premium content, including how-to articles and support forums, as well as priority email support and member exclusive plugin extensions..

 

Today we take one step closer to WP-Members 3.0! Version 2.9.8 includes some updates that lay the groundwork for moving the plugin into the next major version release.

Please be sure to read the release notes prior to updating to determine how you will be affected by these changes. It is always recommended that you test the update on a staging server prior to updating production.

This update does not make any changes to database settings during the update with the exception of the version number. If you need to roll back, the previous version (2.9.7) is available here.  Continue Reading →

WP-Members 2.9.7 native registration error patch

· ·

This article is provided free. Find out how you can get full access to premium content, including how-to articles and support forums, as well as priority email support and member exclusive plugin extensions..

 

The 2.9.7 release of the plugin was intended to include a fix for the native registration to work with localized (translated) sites. Unfortunately, there was a flaw in the line that fixes this. The flaw causes a breakdown of the native (back-end wp-login.php) registration process.

I have patched this in the main plugin download package.  Since I caught this early and the majority of users do not use this backend registration, there aren’t that many users effected.

But if you are one of users effected by this, you have two options.  First, as I just mentioned, the download package is fixed so you can re-download the plugin.  You really only need to replace /wp-members-core.php (and /admin/user-export.php for one other patch).

Or, you can apply the fix yourself.  If editing in WP, go to Plugins > Editor and select WP-Members from the plugin dropdown.  Open the file /wp-members-core.php.

Near the end of the file, the second from the last function is wpmem_wp_reg_finalize.  Line 920 is the first line of this function and you will see:

$native_reg = ( isset( $_POST['wp-submit'] ) && $_POST['wp-submit'] == esc_attr_e( 'Register' ) ) ? true : false;

The esc_attr_e is the problem.  This echos the output and we don’t want that.  This should be changed to esc_attr( __( ‘Register’ ) ) like this:

$native_reg = ( isset( $_POST['wp-submit'] ) && $_POST['wp-submit'] == esc_attr( __( 'Register' ) ) ) ? true : false;

WP-Members 2.8.2 bug fix for “string contains…” when using auto excerpt

· ·

This article is provided free. Find out how you can get full access to premium content, including how-to articles and support forums, as well as priority email support and member exclusive plugin extensions..

 

This is one of those odd things that slips through quality control before a full release package.  There is an artifact in the code that was there for debugging a new feature and this inadvertently made it into the production version.  Continue Reading →

Ready to get started?

Join Today!