Having received an email from the Magento Team the other week bigging-up the latest release of Magento and encouraging me to upgrade as soon as I could, I dutifully upgraded the Mage_Core_Modules to 1.3.0. This appeared to go without a hitch and after I made a couple of adjustments in the admin and tested the fronend I was happy that it was a successful upgrade.
The following day I attempted to login to the Magento admin area only to be presented with a 404 error! Geez, what a pain.
After doing a bit of forum bashing I found the solution I was after:-
http://www.magentocommerce.com/boards/viewthread/37202/P30/#t121336
For those with the same problem as mine… (can’t login after upgrade, and don’t have ssh capabilities,) I have found a workaround. It worked for me, but I can’t guarantee it will work for you, so proceed at your own risk. I am not the most tech-saavy guy, I just figured it out by looking at the error.
1.)The first thing to do is download the entire magento 1.3 package. Unzip it, and go into Magento->app->code->core->Mage->Adminhtml->Model->Url.php Grab the Url.php file.
2.)Go to your server, and into your directory where you have magento installed. go to app->code->core->Mage->Adminhtml->Model and replace the Url.php file.
3. Clear the cache in your browser and try logging in again.
4. At this point, if you were able to get in, I suggest that you go to magento connect and properly upgrade. Worked for me. I hope it works for you.
After following these steps I was able to login without a problem. -phew-
Then, to top it off the dropdown menus were not working in the admin area! Checking Firebug I found this was due to the javascripts 404-ing. Another dose of forum searching it was apparent that this was a common problem (I had experienced it before myself) the /js folder and contents had the wrong permissions following the upgrade.
I opened FireFTP logged into the site and changed the permissions on the /js folder and all it’s contents to 755. This has sorted that problem, so I’m happy now.
All in all it looks like these problems I encountered after the upgrade are now sorted, let’s hope that’s the last of them and the next upgrade will go smoother.