I have never done an upgrade before and am concerned that all my work may be lost.
I have done basic customization stuff to the Magento Cart so far, as that’s all I am capable of. The site is still in an early design stage, so I thought better to upgrade now than latter?
In admin/manage products/add images the ‘Browse Files’ and ‘Upload Files’ buttons do not do anything when I click them, I read that the new upload will solve this problem.
You can upgrade by SSH or Magento Connect - but no matter which way you do MAKE A COMPLETE BACKUP FIRST. I cannot emphasize that enough. Create a working clone of your site - all files and database - and run the upgrade on it to make sure it functions correctly. If that works then go ahead and upgrade your existing site, but you’ll want to make sure you still have a full backup of it in case something goes wrong with the upgrade or there is an element of functionality you forgot to check with the upgrade.
Could you please tell us how you would go about creating a clone WITH the database? When you upgrade, does that change ANYTHING in the database? I have a heavily modified 1.1.6 (only template files though, not core) so would need to do some thorough testing before upgrading. Why, oh why do they have to change the template files every time - makes upgrading a nightmare!
Thank you!
Sure thing, export your database sql and then import it into a separate database. Then duplicate your site files into a new location and connect them to your new database. Probably the easiest way to do that is to delete your app/etc/local.xml file (on your new location) and run the installation again pointing it to the new database. It will keep all your files etc the way they should be and you’ll have a working “clone” of your site.
The best mySQL backup script/utility that I’ve found for a hosted environment is:
http://www.mysqldumper.de/en/
It’s easy to install, easy to use, and it’s FREE. It’s much more configurable than the standard phpMyAdmin that comes with most hosted platforms. You can also set cron jobs to backup all your databases automatically and store the backups as compressed gzip files.
Regardless of which tools you use, backup often or be willing to begin from scratch!
Now, you will have a complete backup of your ‘magento_database_name’ database in magento-db-backup.sql. To import the backup into a new database, you can use this command:
mysql -u mysql_username -p new_database_name < magento-db-backup.sql
To make a copy of your existing store, you can first create a tar archive of all your files, then extract this into a new location.
Make archive: tar -zcf full-backup.tar.gz magento_dir Where 'magento_dir' is the full path to your Magento root directory.
Extract: tar -zxf full-backup.tar.gz This will extract the content of fullbackup.tar.gz into the current directory.
The last step is to edit the app/etc/local.xml to reflect the login credentials of your new database.
PS: this short tutorial is very brief, but should provide some guidance as to how to create a clone of your Magento store.
Sure thing, export your database sql and then import it into a separate database. Then duplicate your site files into a new location and connect them to your new database. Probably the easiest way to do that is to delete your app/etc/local.xml file (on your new location) and run the installation again pointing it to the new database. It will keep all your files etc the way they should be and you’ll have a working “clone” of your site.
Does that make sense?
Hi Sherrie,
Yes, many thanks - that’s very helpful! Much appreciated!
:)
If you’re using SSH and need to use zip files instead of tar.gz files (my server won’t allow me to extract tar.gz files myself; I have to submit a support ticket for it) here are the commands you need:
Sure thing, export your database sql and then import it into a separate database. Then duplicate your site files into a new location and connect them to your new database. Probably the easiest way to do that is to delete your app/etc/local.xml file (on your new location) and run the installation again pointing it to the new database. It will keep all your files etc the way they should be and you’ll have a working “clone” of your site.
Does that make sense?
Thank you Sherrie, this really helped me out.
A little addition that I noticed that may need to be done if you are using the above method to clone a site, When you come to upgrade the clone you get an error on Magento Connect saying that it was unable to find the directory, then it has a reference to the orignal path eg. /website1/public_html
So I used a program called grepWin to search for the word “website1” and it appeared in the /downloader/pearlib/ files
I then simple replaced the “website1” with “clone1” and uploaded the files, then when I ran the Magento Connect upgrade it wont perfectly.
I’m using magento 1.1.6 and want to upgrade to 1.1.8 now.
My problem is in lack of better knowledge I changed some things in the core files to fit my needs. When i upgrade now all of the changes are gone? Is there a way to get megento to keep those changes? The worst thing is i don’t know all places i changed things.
