WP-Members 2.5.2 incremental update now in testing phase

As much as the 2.5 and 2.5.1 releases brought to the WP-Members project, there were still some kinks to work out with the new features.  With the help of some astute users, I’ve tracked down some key issues and have packaged an incremental update in the 2.5 series release and it is in the testing phase.  I hope to release it soon. 

Here is what you will find in this package:

• Admin Menus: fixed this so that the user menu isn’t open by default when the settings menu is open.  The fix for this, as an added bonus, solves a minor security issue with using (__FILE__) for the add_options_page WP function.
• Ignore warning messages: 2.5.1 broke this feature.  It is now corrected.
• reCAPTCHA removed from members settings update page.  It doesn’t need to be here (and wasn’t intended to).
• Sidebar widget and login box: added a <br /> tag for “you are not logged in” which was not displaying a break in some browsers.  Also, IMPORTANT if you are using custom CSS, the widget in the 2.5.1 production version got changed from a <li> tag to <div> and shouldn’t have.  This has been changed back for WP’s automatic widget process.  This changes the ID for the sidebar from #wpmem_login_side to #wp-members (the name of the widget).  If you didn’t customize CSS, you are not effected by this.
• Login process was finally updated to wp_signon (wp_login has been deprecated for awhile and not sure when it’s going to officially disappear, but WP 3.2 is coming out soon, so you never know…)
• For users that might be using reCAPTCHA in another plugin, I updated to check for the reCAPTCHA library before loading it.  That should avoid any collisions and allow you to use WP-reCAPTCHA and others that use the same library.
• Bulk user activation was possible in the primary users view with all users selected.  This allowed the admin to inadvertently reactivate existing users, which resets their password.  I have corrected that so that, while you can have users that are not activated checked, if that user is already activated, it will not reactivate.
• Laying the groundwork for pluggable functions.  This should be considered experimental at this point as some functions will be updated to make this more functional and customizable.  But it’s a start.