Project list for WP-Members 2.5.2 incremental update

I am working on some updates and fixes since the WP-Members 2.5.1 release just a few days ago.  My original intention was to move forward on version 2.6 where I intend to add a process to customize/add/delete registration fields, but there were some minor things that were “bugging” me.  Here is the list as it stands now: 

Projects completed:

Admin menus – this has been bugging me for awhile, but it became more appearant as I began testing in the new WP 3.2 environment (you did know that was coming, didn’t you?) The problem was that when you opened the WP-Members settings menu, the Users menu also opened.  A minor annoyance in the WP 3.1 admin panel, but much uglier in 3.2’s new admin menu.  So I fixed it.  The fix also corrects a minor security issue of using (__FILE__) for the WP function add_options_page, so double bonus.

Since the introduction of reCAPTCHA in the 2.4.0 beta release, no one told me that the reCAPTCHA was (a) showing up in the members settings update page and (b) didn’t work on that page.  OK, I’ll let you all off the hook.  I never mentioned to anyone that it wasn’t supposed to be there.  To me it doesn’t make sense to require reCAPTCHA on a screen that is only accessible by logged in users.  WP doesn’t require you to fill out a CAPTCHA when you update a post or your settings, does it? So, I corrected that little bug.  Thanks to Christian for catching this!

In 2.5.1, the introduction of an additional setting in the settings array (legacy forms) threw off the “ignore warning messages” value for the admin panel.  This is corrected in 2.5.2

I updated the login process to use wp_signon.  wp_login was deprecated awhile ago, and I try to keep up with removing deprecated functions and hooks, since you never know when they will actually disappear.

I will begin introducing pluggable functions in the near future.  The groundwork is beginning to be laid in this release.  I get a lot of customization requests that generally involve tweaks that would be required in the code.  It is always my advice to not go down the road of modifying core code directly if at all possible because this is not upgradeable (and difficult to troubleshoot). Making functions pluggable will allow users to customize without touching core code.

Projects working:

As I mentioned earlier, I am working with the new WordPress 2.3.2 beta.  It is likely that this will usher in Twenty Eleven as the default theme.  I have started working on a stylesheet for Twenty Eleven.  This will initially be included as an optional stylesheet.

Well, that’s where things stand at this point.  As always, I am open to suggestions and requests.  The plugin as it stands now has been very much the product of user input.  I can’t promise every want will make it in, but I make efforts to include the best and most workable ideas into the project list.