I was installing an extension and it failed. Now the page is not loading and showing following error.... Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. After deleting maintenance.flag it shows another error.... Fatal error: Call to a member function extend() on a non-object in /home/wwwthema/public_html/lib/Varien/Simplexml/Config.php on line 600 ... Please give the solution http://themaorishop.co.nz/
1 Answer
If you are using a custom Magento theme and are having problems getting extensions to display correctly on the frontend, there is a good chance that it is an issue of file location. Extensions usually install to default/default/ or base/default/ because there is no way for the developer of an extension to predict whether you are using a custom theme or what its name might be.
When using a custom theme, Magento will look in YOUR_CUSTOM_THEME/default/ directory for an extension’s .phtml, .xml, and .css files. If they were installed to the default or base directory, Magento won’t be able to locate them within the theme directory and consequently the extension’s output won’t be displayed.
To display the output of an extension, simply make sure that its files are in the correct locations. Check the base and default directories and see if there are any CSS, XML, or PHTML files for the extension. If so, move the files to the corresponding location within your custom theme.
Finally, refresh your cache and test that the extension’s output is correctly displaying. Hope it helps :)
-
Yes Erin, it was the same problem you have described. The extension installed at wrong place and it was causing error. Now it's working :)– KishorNov 18, 2014 at 4:08
-
Please accept the answer if it was indeed how you corrected the aforementioned error. Nov 20, 2014 at 5:25
#ini_set('display_errors', 1);
and changeif (isset($_SERVER['MAGE_IS_DEVELOPER_MODE'])) {
toif (isset($_SERVER['MAGE_IS_DEVELOPER_MODE']) || true) {
. Then you should be able to see where the error originates...hopefully.