Magento WizardWelcome to the Number 1 Magento Hosting website.

Contact the site  Make Money

Can’t Load Magento Page – The Error Report Feature

 Add to Favourites  
(0 rating, 2 votes)
Loading ... Loading ...

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!

Be Sociable, Share!

about the author

    This article was written by Sam Davis on November 25, 2008.
    Computing over a glass of Grenache Shiraz... again!
    Sam is the Editor of Blasted Thing. Contact Us

related articles

 The "SQLSTATE[23000]: Integrity constraint violation" error

comments



  • Sponsored Ads

  • Magento Themes
    • baljit: pls helps me gateway error :transction is not accepeted...
  • Recent Tweets