Hello I would like to upgrade from a customized 3.1.8 PRO to 3.2.3. I'm afraid of doing this because it's on a site with many members and new signups+payments every days. I don't know how to do this upgrade in the safest and fastest possible way. Any help would be greatly appreciated. Thank you
Hi I suggest 1 Shedule a downtime period and take website offline to customers 2 Back up Amember Directory 3 Back up SQL database 4 Download 3.2.3 upgrade files 5 In case of customisation to core files use program like "winmerge" to compare changes from original and upgrade files 6 Upload new files once happy that any customisations have been copied over 7 Test all is working as expected 8 Bring website back on line
Hi JJack Thanks a lot for your plan of action. Looks good. There is just one point that I fear I have not control on. I can put the site offline to customers but what about the recurring payments that are received every days from current customers. I receive payment notifications every days and I can't stop those ones (recurring payments received via paypal). If I upgrade the database while payment notifications are being sent, I will have no way to record those payment notifications into the new db. What I could do is create a new install with the new customized files and use a duplicated db. If new install works well, before making it the main one, I would have to check that in the old install no new payment would have been sent. If payment would have been sent, then reduplicate the old database and upgrade it once again etc... Would this work? It seems a little bit complicated and I was wondering if there was not an easier solution? Thanks again for your help.
Actually the only downtime you will get is when you will copy modified files to server. There were not many modifications to database from your version, so new files will likely work with old database. To avoid downtime, just upload modified files to different folder, then swap(rename) folders.
Ah that's a GREAT news thanks! But when you say "not many modifications", it means that some were made, will I have non working features if I don't upgrade the database and if yes which? (I need the multiple paypal addresses feature - hope this will work) Thanks
You must upgrade database as soon as new files will be uploaded. Even if there were not many modifications in database and basic aMember functionality will be ok, you and your users may receive an errors on different aMember parts. As I can see from diff one field was added to coupon table and two fields were added to product_links tables.
Ok I have just updated and there is a problem with coupons that give 100% OFF. When someone tries to subscribe with such a coupon to one of the memberships, paypal displays this error message: Invalid Regular period. You must specify valid values for the A3, P3 and T3 parameters for a subscription. I use this kind of 100% OFF coupons for testing as well as for partners. Any idea?
Actually the only downtime you will get is when you will copy modified files to server. There were not many modifications to database from your version, so new files will likely work with old database. To avoid downtime, just upload modified files to different folder, then swap(rename) folders.