Magento

The first heading will show up as page title.

This guideline will insure you have a stable version of your site installed with the newest version of Magento software. This upgrade procedure does not rely on Connect or FTP.

This is also the recommend procedure for upgrading from Magento CE to Magento EE.

This should be a complete list of items for upgrading the production database, rolling out the new codebase, and transferring DNS resolution to the new Magento instance.

1. Identify and list modules to go to upgraded version
   • You may not need all you modules brought over and some modules will not be compatible in a newer version. Each one must be checked and tested.
   • Make sure to check your Local and Community Folder.
   • If you have a local/Mage folder you will need to check if the code is compatible with the version you are upgrading to.

1. Identify theme components to transfer
   • Make sure all your theme files are in the correct folders and more importantly make sure you theme is compatible with the version you are upgrading to. It is best to test your upgrade on the default theme, then slowing add in just the theme files you need for your theme. There are layout files that are specific to the newer versions of Magento and it is important that these files are used for you install. A good example is checkout.xml.
2. Identify external components that need to function with new version, review on Magento integration options (i.e. does it make sense to make the external app a Magento app or leave it as an external app)
3. Tarball catalog and move to new CE site

1. Export Live database to an SQL dump file (db-YY-MM-DD-pre.sql)
2. Transfer db-YY-MM-DD-pre.sql to the dedicated database upgrade server and imported into the local MySQL instance
3. Execute nohup php index.php > log-YY-MM-DD_1 &
4. Let process run until finished
5. Re-index site
6. Export Upgraded database to an SQL dump file (db-YY-MM-DD-post.sql)
7. Transfer db-YY-MM-DD-post.sql to the production machine and import into the local MySQL instance

1. Correct Store Issues (Update so admin can login!)
2. Execute necessary scripts
3. Enter Admin panel and set the following configuration values:
4. Themes and packages set to default
5. Refresh cache and indexes
6. Turn on “Display out of stock products” System>Configuration>Catalog>Inventory>Stock Options: Display out of Stock Products to “Yes”
7. Update CMS Page and Static Blocks
8. Set order number higher

1. Switch the Apache vhost references to point to the new instance, disable the old instance
2. Restart Apache
3. Site is now live

If you have additional questions you can email Brent W Peterson creativedata@gmail.com

— Brent W Peterson 2011/09/09 10:44