How to upgrade magento 1.4 1.1 to 1.7.0.2

How to upgrade magento 1.4 1.1 to 1.7.0.2 1. Change permissions on lib/pear folder to writable (recursively): command: chmod -R 777 lib/PEAR 2.Execute this command to prepare Magento for upgrade: command: ./pear mage-setup Most likely you will see this result after command execution: Channel “connect.magentocommerce.com/core” is already initialized Upgrade from Magento 1.4.1.x to Magento 1.4.2.0 This step is necessary even if you upgrade your Magento store to 1.5 or 1.6 versions.

3.Execute Magento upgrade command: command: ./pear upgrade -f magento-core/Mage_All_Latest-stable Output of the command will show you what core packages were upgraded: channel://connect.magentocommerce.com/core/Mage_Centinel-1.4.2.0 upgrade ok: channel://connect.magentocommerce.com/core/Interface_Frontend_Base_Default-1.4.2.0 upgrade ok: channel://connect.magentocommerce.com/core/Phoenix_Moneybookers-1.2.3 upgrade ok: channel://connect.magentocommerce.com/core/Find_Feed-1.0.7 upgrade ok: channel://connect.magentocommerce.com/core/Interface_Adminhtml_Default-1.4.2.0 4.When this part of the upgrade will be complete, enter these commands: command: .chmod 550 ./mage command: ./mage mage-setup . Running initial setup...

Success

Successfully added: http://connect20.magentocommerce.com/community

It means that Magento connect 2.0 channel was added to the channels list successfully. 5.Next, enter this command: command: ./mage sync The result will be: Successfully added: community/Lib_Js_Mage-1.4.2.0

Successfully added: community/Lib_Js_Calendar-1.51.1

Successfully added: community/Mage_Downloader-1.5.0.0

Successfully added: community/Lib_Js_TinyMCE-3.3.7.0

Successfully added: community/Lib_Js_Ext-1.4.2.0

Successfully added: community/Lib_Google_Checkout-1.4.2.0

Successfully added: community/Interface_Install_Default-1.4.2.0

Successfully added: community/Lib_Js_Prototype-1.6.0.3.3

Successfully added: community/Find_Feed-1.0.7

Successfully added: community/Lib_LinLibertineFont-2.8.14.0

Successfully added: community/Lib_Varien-1.4.2.0

Successfully added: community/Mage_Centinel-1.4.2.0

Successfully added: community/Lib_Phpseclib-1.4.2.0

Successfully added: community/Mage_All_Latest-1.4.2.1

Successfully added: community/Mage_Locale_en_US-1.4.2.0

Successfully added: community/Lib_PEAR-1.4.0.0

Successfully added: community/Lib_Mage-1.4.2.0

Successfully added: community/Mage_Pear_Helpers-1.0.18800


6.Upgrade from Magento 1.4.2.0 to Magento 1.5.10 or Magento 1.6.0.0 Now you can upgrade your store to version 1.5 or 1.6. Before proceeding with this part of Magento upgrade, it is very important to see to what version Magento upgrade scripts will upgrade your store. Enter this command to check this:

command: ./mage list-upgrades Updates for community:

Lib_Js_Mage: 1.4.2.0 => 1.7.0.1
Lib_Js_Calendar: 1.51.1 => 1.51.1.1
Mage_Downloader: 1.5.0.0 => 1.7.0.1
Lib_Js_TinyMCE: 3.3.7.0 => 3.4.7.0
Lib_Js_Ext: 1.4.2.0 => 1.7.0.0
Lib_Google_Checkout: 1.4.2.0 => 1.5.0.0
Interface_Install_Default: 1.4.2.0 => 1.7.0.0
Lib_Js_Prototype: 1.6.0.3.3 => 1.7.0.0.3
Find_Feed: 1.0.7 => 1.1.1
Lib_LinLibertineFont: 2.8.14.0 => 2.8.14.1
Lib_Varien: 1.4.2.0 => 1.7.0.0
Mage_Centinel: 1.4.2.0 => 1.7.0.0

Lib_Phpseclib: 1.4.2.0 => 1.5.0.0

Mage_All_Latest: 1.4.2.1 => 1.7.0.2

Mage_Locale_en_US: 1.4.2.0 => 1.7.0.1

Lib_Mage: 1.4.2.0 => 1.7.0.1
7.Enter this command to change the upgrade channel to stable: command: ./mage config-set preferred_state stable Result : Success 8.After channel selection you can upgrade your Magento to 1.5.1.0 (or to Magento 1.6.0.0) using this command: command: ./mage upgrade-all --force 9.Clear the Cache and give permissions to magento folders. 10.Replace old .htaccess file insted of new file.



Important notes: 1.When upgrade magento version 1.4.1.1 to 1.7.0.2 that time DB issues occured: Tables List: a.wishlist_item b.Catalog_Category_Flat_Store_30 c.tax_order_aggregated_updated d.sales_order_tax_item Solution: First of all take backup of above tables, After delete those tables issue is resolved. For alternative backup of above data re-import the backup tables. (This tables are not mandatory, just keeping it backup) NOTE: if create any table issue rise in upgrade time take bakup table and delete it. 2.“Integrity constraint violation: 1062 Duplicate entry “
Solution:
This error can be solved by disabling the unique indexes check. In the app/etc/config.xml, change this

SET NAMES utf8 to this SET NAMES utf8; SET FOREIGN_KEY_CHECKS=0; SET UNIQUE_CHECKS=0;

3.Error: Fatal error: Call to a member function getAllOptions() on a non-object in /var/www/html/magento/app/code/core/Mage/Core/Model/Cache.php on line 455

Solution: Uncomment line 198 in app/mage.php:

//self::$_appRoot = null;

which is called by app/code/core/Mage/Core/Model/Config/Options.php at line 54:

$appRoot= Mage::getRoot();

4.Admin Side not disply

Solution:

app/code/core/Mage/Admin/Model/Session.php (Commented Line No:93)