We have a Magento Web Store build with Magento Enterprise Edition version 1.12. We are planning to upgrade it to version 1.14. We understand that we will need to do an incremental upgrade i.e. from 1.12 to 1.13 first and then from 1.13 to 1.14. I have a few questions regarding this as below:
1. Is the plan correct about doing incremental upgrade rather than direct to 1.14?
2. We are planning to do the upgrade via Magento Connect rather than manual or through ssh, should that be ok
3. Our store has around 81 extensions including paid/free, some of them we developed, so does this mean it would be more difficult. Note: only a few are customized and most of them are not and compatibility checks already done.
4. If we go for incremental upgrade, does it mean, we have to pay for version 1.13 too?
5. We have identified following steps, does it make sense or any other/better way to do this?
Backup of complete site and DB and create a new instance where upgrade will happen.
list all extensions and details about them like paid/free, customized/not, licenses etc.
Do the following steps on the new instance created for upgradation.
Enable exceptions logging in the system
|Flush Magento Cache & disable it.|
|Making sure all crons are disabled. Make sure built-in compiler is disabled if enabled|
|Modifying indexers settings to update when scheduled rather than automatic|
|Complete the Upgrade as per Magento Steps using Magento connect. Deprecation errors may come due to PHP pugradation which needs to be handled|
|Delete file named maintenance.flag from root|
|Changing URLs based on changes to 1.13 using URL redirect scripts. [Magento install dir]/php -f shell/url_migration_to_1_13.php - thread-count. thread-count is the number of CPU cores in Magento server, minus 1, to a maximum of 15|
|Full re-indexing from command line.|
[Magento install dir]/php -f shell/indexer.php — –reindexall
. Make sure to check if all URLs work in this instance
clear [Magento install dir]/var/cache /var/full_page_cache /var/locks
|enable crons, enable cache, modify indexer settings and make it default (update when scheduled) and delete the /var directory. If built-in compiler was disabled then re-enable it|
|Review all extensions one by one and compare functionalities related to each extensions with Live instance and make sure they work as they should on upgraded version|
|Making sure all custom code is applied to the upgraded version|
|Verify complete web store functionalities are working|
I would appreciate some insight on this. Are we missing anything here?
Here are my views:
1) You can directly upgrade your store to 1.14.
2) Yes, you can directly upgrade your store from magento connect.
3) There will be no issue as you have already checked for the compatibility. Please make sure your customized extension code is in your theme. If it's not in your current theme then its override by the latest files.
4) I'm not sure but I have a good feeling that you don't need to pay for the updates like these.
5) The steps you have metioned are good to go
I appreciate your time in responding to my questions and going through the list i mentioned.
I posted same question in stackexchange and as per that, it won't be possible to go for the Magento Connect way. Here is a link to that http://magento.stackexchange.com/questions/64639/upgrading-existing-store-from-magento-enterprise-ed...
It is possible with Magento Connect. You can follow either process.