-
Categories
- 10% Off Magento Themes with ECommerce-Themes.com
(+2 rating, 2 votes) - Magento Single Page Checkout - Video Guide (+1 rating, 1 votes)
- USA Magento Hosting with A2 (+1 rating, 1 votes)
- Secpay Module for Magento (+1 rating, 1 votes)
- Banishing Insecurities When Shopping on the Web (+1 rating, 1 votes)
-
- 03 visitor(s) online
Online Visitors
-
Recently Written
- Change Credit/Debit Card Name in Magento
- Export List of Magento Orders in CSV Format
- The “SQLSTATE[23000]: Integrity Constraint Violation” Error
- Display Custom Static Text Block on Home Page - Video Guide
- Display Products on Magento Home Page - Video Guide
- Magento Single Page Checkout - Video Guide
- Magento Admin System - Video Guide
- Export Magento Products into Google Base
- Use a Coupon Code for Specific Products or Categories in Magento
- Clicktale - Record User Actions and Mouse Movement Videos on Your Site
-
Links
-
Admin
Can’t Load Magento Page - the Error Report Feature
 Add to Favourites
 Email This Post
| Very handy...    |
While you’re playing around with Magento, at some stage you’re more than likely to see an error page which says “Whoops, our bad…” - not a pretty sight! This usually happens when you’ve been playing around in Admin, and you’ve referenced a file or template that doesn’t exist. At first, when I saw these errors, I wondered how on earth I was going to fix it - considering the error message is completely non-descriptive!
However, if you take a look at the URL, you’ll see a long numerical Error ID. This ID is important, because you need to access a file via FTP with this file name - and this will enable you to see which template contains the error.
The directory in question is /var/report.
Simply open this folder, locate and open the file which matches the number in the ID. This is your error report. Starting a few lines down you should see something which says something like…
1 2 3 | #1 /home/domains/domain.com/public_html/app/code/core/Mage/Core/Block/Template.php(131): include('/home/...') #2 /home/domains/domain.com/public_html/app/code/core/Mage/Core/Block/Template.php(163): Mage_Core_Block_Template->fetchView('frontend/defaul...') #3 /home/domains/domain.com/public_html/app/code/core/Mage/Core/Block/Template.php(180): Mage_Core_Block_Template->renderView() |
It is the first line (#1), that has the template which shows you where the error lies. Chances are, you have tried to reference another template or a file that doesn’t exist - so check and re-check - and if in doubt, restore the file from backup.
Unfortunately, Magento has a nasty habit of bringing your whole site down with this “Our bad..” error, which really isn’t great - it’s a shame that one awry character can affect a whole site. However it certainly does encourage you to check and re-check your work - no-one wants to see a website go down!
If you get this error, I do sympathise with you - but now you know how to sort it!
about the author
This article was written by Sam Davis on November 25, 2008.
Computing over a glass of Grenache Shiraz... again! Sam encourages you to make money by writing articles for us! Learn More |
related articles
comments
Leave a Reply
-
Sponsored Ads
-
The New Blasted Thing
Blasted Thing has recently undergone an essential re-design, as we prepare to welcome a host of new features in to our web-site.
We will continue to be gathering useful articles, tutorials and advice regarding Magento - and we'll be focusing on a number of hosting and theme companies which we have independently verified. -
Translate this page
Translate
|
Just wanted to say that Inline translating is the best thing ever. I love magento....
|
