Today on the aMember forums Alex announced a new version: aMember Version 3.1.9 Released.
Release target: bugfixes, improvements, new plugins
Changes since 3.1.8
- member.php (Membership Information Page) inteface improved with “tabs”
- “Rebuild Db” now handling data in chunks, this improves work with big databases;
- Fixed issues with PayPal plugin (new PayPal accounts);
- Recurring billing implemented for PayPal Pro plugin;
- Google Checkout plugin fixed and improved for recurring billing;
- Single-login fixed in vBulletin4 plugin;
- Added ability to export expired users;
- PHPMailer library upgraded to 2.0.4;
- Added ablility to e-mail more than one notification about not-completed payment;
- Verotel plugin has been fixed;
- More than 200 small fixes and improvements to the core source and plugins;
What this means to me and you is that now I’ve got to go through all of my aMember plugins and make sure they are compatible with the new version so they are ready for anyone who wants to upgrade. That’s going to take me a little while.
Many of the files that have been upgraded are files you have to modify for my plugins.
I’ll keep you updated on my progress and I’ll try to make some improvements to my plugins while I’m in there if I can.
I put version numbers in my plugins so you will know what the last version of aMember was that was tested with them.
For instance you might see a version of 3.1.8.6 which tells you that it was last tested with version 3.1.8. So when you go to the download page for one of my plugins and it says it is version 3.1.9.0 then you will know that I’ve tested it and updated it if I had to so it will work just fine with 3.1.9. Until you see that version however, there is no guarantee that it will indeed be alright. When it does happen, look for some special instructions to be sure that there isn’t something important to do when you upgrade.
I’ll post more on this later as I go through my plugins.
I’m just wondering if there’s really any compelling reason to upgrade. Since I have amember working reliably, the thought of jumping in and updating PHP files gives me pause, to put it mildly.
- John
Thanks for the heads up Ken!
QUESTION: Can we just stay with the current 3.18 version…if we’d rather avoid the hassle of updating everything?
Thank you! I will look forward to upgrading once I know your plugin(s) will still work.
This is not a critical update. There aren’t any security fixes. It looks like it will be really nice to have, but if your site doesn’t have any of the problems they have mentioned fixing then you’re safe to leave it the way it is for now.
If you’re using any of my plugins (which you are if you are reading this and commenting. ;-D) then you will want to wait until I test them with the new version.
Once I do that, it will be important to note that the plugin won’t necessarily be backwards compatible to 3.1.8. So if you stick with 3.1.8 of aMember you won’t be able to upgrade to version 3.1.9.x of my plugin (in some cases…we’ll have to see. Each one will be noted.)
Make sense?