Complex Upgrade

Discussion in 'Installation' started by microlinx, Nov 10, 2006.

  1. microlinx

    microlinx Member

    Joined:
    Oct 26, 2004
    Messages:
    268
    Hello Alex!

    I have been meaning to do an upgrade and database move from one domain to another. But there are several issues that I am not sure about...

    The situation:
    1. I have the script running on one domain, which we'll call "domain_A.com".
    I would like to move the script to "domain_B.com".
    2. The current "domain_A install" is at version 2.3.5 Pro.
    3. The database contains about 8500 members.
    4. I have paid licenses for both domains.
    5. Domain_B.com has the latest version of aMember installed. (3.0.7 vanilla, no mods or customization) and NO database or settings.

    The plan:
    I need to move my "domain_A.com" installation to "domain_B.com".

    The problem:
    1. How do I convert my existing 2.3.5 database to a 3.0.7 compliant version?
    2. Database prefix for the db and user will change. Is that a problem?
    (ie: domaina_dbname & domainb_dbname...)
    3. Can I retain my custom pages in /templates or is it recommended that I redo those pages.

    If there is a post somewhere that explains the upgrade proceedure, please reply with that link.
  2. alex

    alex aMember Pro Customer Staff Member

    Joined:
    Jan 24, 2004
    Messages:
    6,021
    1. You dump your database from A (using phpMyAdmin in webhosting control panel) and save it to a .sql file.
    2. You go to phpMyAdmin on server B and load .sql file into an empty database you created for aMember.
    3. You copy file amember/config.inc.php from A to B and change database connection settings.
    4. You use script http://www.amember.com/downloads/fixlicense.zip to fix root URL and license key in database on server B.
    5. You access http://www.serverB.com/amember/admin/upgrade_db.php
    and database will be automatically converted to 3.0.7.
    6. Viola, you can use aMember on serverB. Don't forget to re-protect folders using aMember CP -> Protect Folders.

    Unfortunately, templates are not compatible between 2.x and 3.x so cannot be just copied.

Share This Page