Last night I was working on installing the new version of Magento to try out some new cool themes and extensions. I did everything exactly as how I installed Magento 1.3. I uploaded the entire Magento folder to my site root. I installed the sample data on the database. Finally, I changed the permission of folders and prepared to install Magento. Then, the error tried to get me:

“There has been an error processing your request. Exception printing is disabled by default for security reasons.”

What was wrong? I have spent nearly half an hour, prepared everything and now got caught by this error? The error wasn’t even kind enough to show me why it said that. So I spent an hour, dig through forum board, Internet and so on and I found some interested tips that I want to share with you today about my experience in installing and updating your Magento store to a newer version. Actually, this is the only time I hope this post will not be useful in the future because I hope Magento will fix it in the next version. Otherwise, you will need to stick with this post for a long long time

Quick fix for “There has been an error processing your request. Exception printing is disabled by default for security reasons.”

This fix is not mine. It was from the Magento community. However, I will post it right here so you won’t waste time clicking and reading people comments in the forum.

1. Step 1: Go to the folder where you install Magento, I will call it siteroot from now on. Go to siteroot/errors
2. Step 2: Change the file local.xml.sample to local.xml
3. Step 3: Go to your Magento store, hit Refresh (F5). You will see the error more clearly.

How to fix “Invalid argument supplied for foreach … toolbar.phtml”

Brightyoursite.com has a wonderful article on how to solve this issue. Please click here to solve your problem right away.

How to fix “SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘awahq_mage.mage_sales_flat_order’ doesn’t exist” error

This error often comes up when you upgrade your Magento software or you have already loaded sample data and install Magento 1.4.1.0 from scratch. The best way to fix this problem will be:

1. Clean all the cache: Go to siteroot/var, delete everything except for .htaccess file.
2. Delete the database: Go to your phpMyAdmin, delete the whole database.
3. Then, install Magento from scratch again. Woo hoo! It works for me now! How’s about you?

The best way to upgrade Magento, people!

Through my experience, the best way to update your Magento software is INSTALL IT FROM SCRATCH. Yes, you hear me. Install everything from scratch and then, migrate old data to a new data and then switch to a new version. The benefit of this approach is:

• You can prevent any errors to your real store. In real world, error-free store makes money. Disrupt store kills your business!
• You can try everything with Magento 1.4 before you roll it out. You can try new themes, extensions and some new features in the new version without causing any harms and effects to the main store
• And the best of all, saving money and time dig through forum and help posts because of stupid Magento errors

Question, comments?

Hit me in the comment section below and I am more than willing to help.

Tags: magento erro, upgrade magento