Magento Linux Upgrade from 1.6.0, 1.6.1 or 1.6.2 to 1.7.0.0
If you are not afraid of Magento Magic, just use the yoursite.com/downloader/
It seems to be the best way.
Upgrade via SSH version 1.6 to 1.7
1. Put your site into maintenance mode. This can often be as simple as editing your “/etc/apache2/sites-enabled/default” file to point to a custom “park” page that you have created to let your customers (and Google) know that your site is only temporarily down. However, if you are doing this right, you will do this upgrade on a VALIDATION SERVER (i.e. a test environment) and get all of the quirks worked out before rolling it out into production. Here is a PRO TIP from an SEO Guru (cr8s.net): Setting the HTTP headers on your temporary “park” page that lets your visitors know that you’re down for a bit to provide status code 502 (service temporarily unavailable) will buy you a little more time in case a search engine crawler comes and sees that your site is down. You should be able to get away with downtimes of up to 24 hours (or 30 to 60 minutes on very high traffic sites) without seeing a penalty to your search engine rankings. Of course, none of this will be an issue if you are using a VALIDATION ENVIRONMENT / TEST SERVER to do this upgrade, which you should DEFINITELY be doing.
If you just did an upgrade to magento or for some reason you try to log into the admin and you cant...and you do not get any errors...its more than likely a caching issue.
remove everything from the var/cache folder
Get to your root of your magento install
cd /var/www/magento_root_location_on_your_server/
rm -rf var/cache/*
Dump your browser cache/history and try again..OR just try a different browser, I bet it will work.
To fix this issue delete the tmp directory (if there is one) and re-create it with 755 permissions. Make sure the owner and group of the directory correspond with the user/group that owns the rest of the website files.
This is the most comprehensive description of the Magento 1.3.x, 1.4.x, 1.5.x, 1.6.x and 1.7.x upgrade process.
Additionally It contains step-by-step instructions and troubleshooting information.
Prepare for Magento upgrade (this part of the article is for old 1.3.x, 1.4.x versions only)
Lets imaging that you have old Magento 1.3.x - 1.4.x store and you need to upgrade it to latest Magento 1.7.x version. First of all it is highly recommended to backup your live store files/database and disable Magento compiler cache.
Next you need to get SSH access from your hosting provider and connect to your server via SSH protocol (using Linux command shell or Putty SSH client for Windows).
After connection via SSH, go to your store folder and execute these commands:
1 - Change permissions on lib/pear folder to writable (recursively):
I struggled with an issue that bugged me for a few hours. I noticed that var/cache was empty! That was strange..so I did some research and this happened right after I setup apc and memcached.
It turns out the the instructions i followed was saving them into memcached instead of the file system under var/cache
Here is what my app/etc/local.xml looked like:
<cache>
If this next line was not commented out, it was going to be saved to memcached and NOT the file system
What’s the easiest way to make an .htaccess file in Unix/Linux so that a directory is password protected? Suppose that your home directory is /home/matt and all your webstuff is in /var/www/protected/ . Follow these steps:
Make an .htpasswd file. The htpasswd command in Unix does this. You should put the password file outside of your web directory. So a command like "htpasswd -bc /var/password/.htpasswd admin mysecretpassword" will create a new file using a username of admin and a password of mysecretpassword into the file /var/password/.htpasswd . At the prompt type "cat /var/password/.htpasswd" it will show you something like: "admin:E.mx8CsZffRI6".
Make an .htaccess file located at /var/www/protected/.htaccess and use the following AuthUserFile /var/password/.htpasswd AuthName EnterPassword AuthType Basic require valid-user