Difference between revisions of "Migration from legacy aMember Pro v3"

From aMember Pro Documentation
Jump to: navigation, search
Line 18: Line 18:
  
 
Install v4 into a temporary folder, try to configure everything you expects from it to do. Configure payment systems, make test products. Ensure that system is working on your host.<br>  
 
Install v4 into a temporary folder, try to configure everything you expects from it to do. Configure payment systems, make test products. Ensure that system is working on your host.<br>  
 +
    During import and the following database rebuild, keep aMember e-mailing disabled. Go to ''aMember CP -> Setup -> E-Mai''l and set ''Email Sending method'' to ''disabled''.
  
 
== Make test conversion  ==
 
== Make test conversion  ==

Revision as of 08:33, 15 December 2011

Contents

Introduction

aMember Pro version 4 is totally different from all previous versions. It uses other database schema, API calls and other templates syntax. It means that all customizations that have been done earlier will be lost and must be re-done for new version. Fortunately, the new version is much more flexible, so many customisations are simply not required.

Right now (as of Dec/01/2011) we do not recommend to upgrade established aMember Pro v3 websites. Some time must pass until we port more plugins, and get additional confirmation of core stability. We highly recommend to use version 4 for new websites, as on new sites any problems are obvious, are easy to detect and to fix. If you are anyway eager to move to version 4, read on.

Current Limitations

  • Automatic import imports products,users, payments, affiliate information with commissions and newsletter subscriptions from v3. Everything else has to be re-configured manually;
  • Non-Recurring subscriptions must be imported without any problems;
  • Recurring subscriptions are known to work correctly for PayPal subscriptions only. Import of recurring subscriptions from other payment systems requires attention from qualified aMember professionals. The problem is not import itself, the problem is how these imported subscriptions will be automatically handled by new payment plugins in v4.
  • Credit Card information is not imported from version 3 by current import script. For now, the decision has made to do not store credit card information in aMember v4. We will offer a path to convert and use Authorize.Net CIM or similiar services for your clients and your safetly.

Try to use v4 

Install v4 into a temporary folder, try to configure everything you expects from it to do. Configure payment systems, make test products. Ensure that system is working on your host.

   During import and the following database rebuild, keep aMember e-mailing disabled. Go to aMember CP -> Setup -> E-Mail and set Email Sending method to disabled.

Make test conversion

  1. Remove all products and users from your testing aMember v4 database. Go to aMember Cp -> Setup -> Plugins and enable aff and newsletter modules (if desired).
  2. Go to your test installation of v4, and open in browser http://www.example.com/amember4/admin-import3 (in URL replace http://www.example.com/amember4 to URL of your testing v4 installation);
  3. Into the form, enter database settings of aMember Pro v3 database (you may find it in file amember/config.inc.php inside amember v3 folder);
  4. It takes time to make import and encrypt passwords, but sooner or later it will import all products and user records.
  5. If you had affiliate program working, you may run next step of import and import affiliate informaton;
  6. If you had newsletters subscritpions set, you may run next step of import and import newsletter threads and subscriptions;
  7. Now you are all set. Go to (v4) aMember Cp -> Rebuld Db and run rebuild.
  8. Test imports results to ensure you see users, payments in place. Check all product settings. Note that you need to reconfigure:
    • Product dependencies: at aMember CP -> Manage Products -> Edit;
    • Autoresponders and expiration e-mails: at aMember CP -> Protect Content -> E-Mail Messages
    • Newsletter threads: check at aMember CP -> Protect Content -> Newsletters
    • Warning! Do not re-protect folders already protected with aMember Pro version 3 on this stage!


If everything went OK with test conversion, you may decide to start full conversion.

Final upgrade to version 4 from version 3

  1. Take note of protected folders (v3) at aMember CP -> Setup -> Protect Folders. Copy/paste customized e-mail messages you've configured in v3;
  2. IMPORTANT! Backup entire aMember version 3 folder;
  3. IMPORTANT! Backup aMember version 3 database;
  4. Rename aMember Pro version 3 folder (usually amember) to something like amemberv3-moved-20111201
  5. Install new aMember Pro version 4 into the same folder where aMember v3 had been installed;
  6. Go to (v4)aMember CP -> Setup -> Plugins, and enable all necessary plugins and modules;
  7. Configure the enabled plugins and modules at aMember CP -> Setup -> [ModuleName']
  8. Go to aMember Cp -> Setup -> Advanced and enable Use aMember3 compatible urls checkbox; that way URLs amember/login.php , amember/member.php and the following will start to work again;
  9. Go to http://www.example.com/amember/admin-import3 (in URL replace http://www.example.com/amember to URL of your new v4 aMember);
  10. Into the form, enter database settings of aMember Pro v3 database (you may find it in file amember/config.inc.php inside amember v3 folder);
  11. It takes time to make import and encrypt passwords, but sooner or later it will import all products and user records.
  12. If you had affiliate program working, you may run next step of import and import affiliate informaton;
  13. If you had newsletters subscritpions set, you may run next step of import and import newsletter threads and subscriptions;
  14. Now you are all set. Go to aMember Cp -> Rebuld Db and run rebuild.
  15. Test imports results to ensure you see users, payments in place. Check all product settings. Note that you need to reconfigure:
    • Product dependencies: at aMember CP -> Manage Products -> Edit;
    • Autoresponders and expiration e-mails: at aMember CP -> Protect Content -> E-Mail Messages
    • Newsletter threads: check at aMember CP -> Protect Content -> Newsletters
    • Re-protect folders that were previously protected (look at step #1)
    • Re-enter custom e-mail messages as aMember CP -> Setup -> E-Mail. Note the new variable names and syntax.
  16. If you had your own test user record in v3, use it to login into member area and ensure you get access to protected folder;
  17. Try to make new signup and payment. Ensure that you've received access to protected folder, and got a welcome e-mail.
  18. Upgrade is finished!