Comments on: Issues with moving Magento from one server to another http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another Blog site of Branko Ajzele, web application developer. Thu, 09 Sep 2010 17:45:00 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: jonathanday http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-4619 jonathanday Tue, 23 Feb 2010 14:44:55 +0000 http://activecodeline.com/?p=806#comment-4619 Thanks Kyle, this just saved me. The media/*/cache and media/tmp folders were causing broken images on my pages - much appreciated. <br><br>JD Thanks Kyle, this just saved me. The media/*/cache and media/tmp folders were causing broken images on my pages – much appreciated.

JD

]]> By: Paul Grant http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-4109 Paul Grant Thu, 30 Jul 2009 09:20:39 +0000 http://activecodeline.com/?p=806#comment-4109 Hi, @Romain : Give it up, you're never going to successfully upgrade a Magento store over that development distance. Too much has changed within Magento, we're wary of going from 1.2.x upwards and would never undertake the upgrade of a store of that age. Your better option there is to create a new store and export/import products, templates etc. I'm also wondering if anyone has had any success with the truncating of store logs. I'm trying to upgrade a 1.3.1.x store, that has never run with the cron (therefore the store logs have never been cleaned), one of the tables runs to 1.5 million entries. I've had the cron attempting to clean the tables for 80 minutes now and i'm becoming impatient! Paul. Hi,

@Romain : Give it up, you’re never going to successfully upgrade a Magento store over that development distance. Too much has changed within Magento, we’re wary of going from 1.2.x upwards and would never undertake the upgrade of a store of that age. Your better option there is to create a new store and export/import products, templates etc.

I’m also wondering if anyone has had any success with the truncating of store logs. I’m trying to upgrade a 1.3.1.x store, that has never run with the cron (therefore the store logs have never been cleaned), one of the tables runs to 1.5 million entries. I’ve had the cron attempting to clean the tables for 80 minutes now and i’m becoming impatient!

Paul.

]]> By: Paul Grant http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-5585 Paul Grant Thu, 30 Jul 2009 09:20:00 +0000 http://activecodeline.com/?p=806#comment-5585 Hi, @Romain : Give it up, you're never going to successfully upgrade a Magento store over that development distance. Too much has changed within Magento, we're wary of going from 1.2.x upwards and would never undertake the upgrade of a store of that age. Your better option there is to create a new store and export/import products, templates etc. I'm also wondering if anyone has had any success with the truncating of store logs. I'm trying to upgrade a 1.3.1.x store, that has never run with the cron (therefore the store logs have never been cleaned), one of the tables runs to 1.5 million entries. I've had the cron attempting to clean the tables for 80 minutes now and i'm becoming impatient! Paul. Hi,

@Romain : Give it up, you’re never going to successfully upgrade a Magento store over that development distance. Too much has changed within Magento, we’re wary of going from 1.2.x upwards and would never undertake the upgrade of a store of that age. Your better option there is to create a new store and export/import products, templates etc.

I’m also wondering if anyone has had any success with the truncating of store logs. I’m trying to upgrade a 1.3.1.x store, that has never run with the cron (therefore the store logs have never been cleaned), one of the tables runs to 1.5 million entries. I’ve had the cron attempting to clean the tables for 80 minutes now and i’m becoming impatient!

Paul.

]]> By: branko http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-4102 branko Tue, 28 Jul 2009 21:04:19 +0000 http://activecodeline.com/?p=806#comment-4102 Actually I use much more easier approach these days. Setup the Virtual host on your local apache to fully reflect the live site. Then create the database and database user on local site with the same name as you have on live site. All you have to do later is simply copy paste the files of Magento site and transfer database. No need to do any search-replace. Actually I use much more easier approach these days. Setup the Virtual host on your local apache to fully reflect the live site. Then create the database and database user on local site with the same name as you have on live site. All you have to do later is simply copy paste the files of Magento site and transfer database. No need to do any search-replace.

]]> By: branko http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-5584 branko Tue, 28 Jul 2009 21:04:00 +0000 http://activecodeline.com/?p=806#comment-5584 Actually I use much more easier approach these days. Setup the Virtual host on your local apache to fully reflect the live site. Then create the database and database user on local site with the same name as you have on live site. All you have to do later is simply copy paste the files of Magento site and transfer database. No need to do any search-replace. Actually I use much more easier approach these days. Setup the Virtual host on your local apache to fully reflect the live site. Then create the database and database user on local site with the same name as you have on live site. All you have to do later is simply copy paste the files of Magento site and transfer database. No need to do any search-replace.

]]> By: Lise http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-4074 Lise Fri, 24 Jul 2009 15:24:28 +0000 http://activecodeline.com/?p=806#comment-4074 After I found this site, moving stores from live to dev and back - has been a walk in the park :-) Thank you Branko! However, this time, it doesn't work at all. So if you have ever run into (and solved) the following problem, I would love to hear your solution: (1)Exported sql database via SSH, (2)searched/replaced "live.com" to "dev.com", (3)imported database. (4)Copied file structure from live server to dev server. Output in browser: Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 71: parser error : Opening and ending tag mismatch: default line 46 and reference in /*/*/*/*/www/app/code/core/Mage/Core/Model/Layout/Update.php on line 294 I've seen a lot of threads regarding people having the same issue - but no answer anywhere :( After I found this site, moving stores from live to dev and back – has been a walk in the park :-) Thank you Branko! However, this time, it doesn’t work at all. So if you have ever run into (and solved) the following problem, I would love to hear your solution:

(1)Exported sql database via SSH, (2)searched/replaced “live.com” to “dev.com”, (3)imported database. (4)Copied file structure from live server to dev server.

Output in browser: Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 71: parser error : Opening and ending tag mismatch: default line 46 and reference in /*/*/*/*/www/app/code/core/Mage/Core/Model/Layout/Update.php on line 294

I’ve seen a lot of threads regarding people having the same issue – but no answer anywhere :(

]]> By: Lise http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-5583 Lise Fri, 24 Jul 2009 15:24:00 +0000 http://activecodeline.com/?p=806#comment-5583 After I found this site, moving stores from live to dev and back - has been a walk in the park :-) Thank you Branko! However, this time, it doesn't work at all. So if you have ever run into (and solved) the following problem, I would love to hear your solution: (1)Exported sql database via SSH, (2)searched/replaced "live.com" to "dev.com", (3)imported database. (4)Copied file structure from live server to dev server. Output in browser: Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 71: parser error : Opening and ending tag mismatch: default line 46 and reference in /*/*/*/*/www/app/code/core/Mage/Core/Model/Layout/Update.php on line 294 I've seen a lot of threads regarding people having the same issue - but no answer anywhere :( After I found this site, moving stores from live to dev and back – has been a walk in the park :-) Thank you Branko! However, this time, it doesn’t work at all. So if you have ever run into (and solved) the following problem, I would love to hear your solution:

(1)Exported sql database via SSH, (2)searched/replaced “live.com” to “dev.com”, (3)imported database. (4)Copied file structure from live server to dev server.

Output in browser: Warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 71: parser error : Opening and ending tag mismatch: default line 46 and reference in /*/*/*/*/www/app/code/core/Mage/Core/Model/Layout/Update.php on line 294

I’ve seen a lot of threads regarding people having the same issue – but no answer anywhere :(

]]> By: Romain Carrere http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-4068 Romain Carrere Thu, 23 Jul 2009 14:15:01 +0000 http://activecodeline.com/?p=806#comment-4068 We're upgrading a magento site from 1.1.8 to 1.3.2.2 and experiencing the same kind of issue... Magento database migration - when upgrading magento or moving to another server - seems to give problems to many people. Even magentocommerce forums is full of "foreign key" issues but Varien does not give us the minimum information for being bale to make it work. @Branko : are you sure about the sql clean script you gave ? I read many times that log_*_type were not to be truncated. Same for log_quote. Has anyone tried this log cleaning ? Did it solved the foreign key issue or did it make other problem appear ? Thanks for sharing We’re upgrading a magento site from 1.1.8 to 1.3.2.2 and experiencing the same kind of issue…
Magento database migration – when upgrading magento or moving to another server – seems to give problems to many people. Even magentocommerce forums is full of “foreign key” issues but Varien does not give us the minimum information for being bale to make it work.

@Branko : are you sure about the sql clean script you gave ?

I read many times that log_*_type were not to be truncated.
Same for log_quote.

Has anyone tried this log cleaning ? Did it solved the foreign key issue or did it make other problem appear ?

Thanks for sharing

]]> By: Romain Carrere http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-5582 Romain Carrere Thu, 23 Jul 2009 14:15:00 +0000 http://activecodeline.com/?p=806#comment-5582 We're upgrading a magento site from 1.1.8 to 1.3.2.2 and experiencing the same kind of issue... Magento database migration - when upgrading magento or moving to another server - seems to give problems to many people. Even magentocommerce forums is full of "foreign key" issues but Varien does not give us the minimum information for being bale to make it work. @Branko : are you sure about the sql clean script you gave ? I read many times that log_*_type were not to be truncated. Same for log_quote. Has anyone tried this log cleaning ? Did it solved the foreign key issue or did it make other problem appear ? Thanks for sharing We’re upgrading a magento site from 1.1.8 to 1.3.2.2 and experiencing the same kind of issue…
Magento database migration – when upgrading magento or moving to another server – seems to give problems to many people. Even magentocommerce forums is full of “foreign key” issues but Varien does not give us the minimum information for being bale to make it work.

@Branko : are you sure about the sql clean script you gave ?

I read many times that log_*_type were not to be truncated.
Same for log_quote.

Has anyone tried this log cleaning ? Did it solved the foreign key issue or did it make other problem appear ?

Thanks for sharing

]]> By: Charles http://activecodeline.com/issues-with-moving-magento-from-one-server-to-another/comment-page-1#comment-4051 Charles Wed, 15 Jul 2009 12:37:37 +0000 http://activecodeline.com/?p=806#comment-4051 I've also had my share of wall-head-bangin' when migrating magento... For me, the best solution to dump the database is via SSH, with the mysqldump command. Everything else (phpmyadmin, magento backup) ended up making me struggle in one point or another. the entire command goes like this: mysqldump -u [usernamedb1] -p [dbname1] > [filename].sql After sended to the target server, the following command imports the .sql file into the desired database: mysql -u [usernamedb2] -p [dbname2] < filename.sql And then it's done (and one of the reasons i love SSH ^^). In case of duplicaded entries, i use the search in phpmyadmin (excellent search, by the way) to find and delete the mothersuckin' thing :) Nice work and nice blog, Branko! Keep up like that! I’ve also had my share of wall-head-bangin’ when migrating magento… For me, the best solution to dump the database is via SSH, with the mysqldump command. Everything else (phpmyadmin, magento backup) ended up making me struggle in one point or another. the entire command goes like this:

mysqldump -u [usernamedb1] -p [dbname1] > [filename].sql

After sended to the target server, the following command imports the .sql file into the desired database:

mysql -u [usernamedb2] -p [dbname2] < filename.sql

And then it’s done (and one of the reasons i love SSH ^^). In case of duplicaded entries, i use the search in phpmyadmin (excellent search, by the way) to find and delete the mothersuckin’ thing :)

Nice work and nice blog, Branko! Keep up like that!

]]>