1. Clone your website (make sure you block Google from indexing your staging site)
2. Set up your staging site with your desired Magento version (once it is installed, remember to remove index.phtml file otherwise it will not load index.php)
3. Connect the X.X.X.X (new version) local.xml to the X.X database (old version) by getting the database from old version app/etc/local.xml
4. In config.xml (for the new version) you will see a line containing “SET NAMES utf8” which needs to be replaced by a new line
<!–<initStatements>SET NAMES utf8</initStatements> –>
<initStatements>SET NAMES utf8; SET FOREIGN_KEY_CHECKS=0; SET UNIQUE_CHECKS=0;</initStatements>
5. Clean new version’s cache and load the back end until getting a “Time out” error, from here wait until the database has finished syncing.
You will notice this by running top or going directly to mysql: mysql -u root -p (pass: 32SvD5ozmsql) and then showing process list;
6. Change the redirection coming from you old website’s database in the table named “core_config_data”,”base_url field” (i.e link: http://184.108.40.206:8081/phpmyadmin/) and clean the cache.
7. If the front end is still being redirected, go to the back end and edit Config>General>Web >Base Url to change to the correct store scope. Also, change URLs to the correct ones.
8. Bring /media/ directory over via SSH
cd to /var/www/merca1702.magecolombia.com/web
rsync -avh ../../merca.magecolombia.com/web/media/ media/
“using ‘relative’ paths, not absolute paths”
9. Reindex “php shell/indexer.php –reindexall” otherwise you may get an error like this:
“Product Flat Data index process unknown error:
exception ‘PDOException’ with message ‘SQLSTATE: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs’ in /var/www/clients/client2/web36/web/lib/Zend/Db/Statement/Pdo.php:228”
So, we need to override some core code, it’s a mysql limitation when you have too many attributes
mkdir -p app/code/local/Mage/Eav/Model/Entity/Attribute/
cp app/code/core/Mage/Eav/Model/Entity/Attribute/Abstract.php app/code/local/Mage/Eav/Model/Entity/Attribute/
change Line 677
‘type’ => ‘varchar(255)’
‘type’ => ‘varchar(64)’
10. Clean the cache and reindex
Upgrade Magento through SSH:
1. Change to your Magento installation directory:
2. Download Magento 220.127.116.11 from MagentoCommerce.com:
3. Extract the archive:
tar -zxvf magento-18.104.22.168.tar.gz
4. Sync files from new (~/magento) version to the old one (~/web)
rsync -avh magento/ ../web/
5. Clean cache
6. Try to load the back end, wait until you get a 504 error, check the server to check msql (top) and wait until it calms down.
From the team at DHD, good luck with your next Magento upgrade and we hope our guide can help you easily walk through the process.