My Magento login admin page has a FATAL ERROR / WHITE SCREEN

I've looked at the other questions which were similar but haven't been able to fix it. My site is at Problem:

Attempts to Fix:

Another post said to:

"In your app/etc/local.xml set disable_local_modules to true and check. If it loads fine then the issue is in one of your custom modules"*

Clear Cache

I followed these instruction but the Admin login page is still a white screen.



::::::::::::One of the files in /var/report there was an error:::::::::::::

  • from your index.php uncomment the line #ini_set('display_errors', 1); Commented Jul 11, 2014 at 11:26
  • Set debugging mode on. Post that fatal error here Commented Jul 11, 2014 at 11:51
  • Check for PHP memory limit.
    – Sukeshini
    Commented Jul 11, 2014 at 11:55
  • Check error logs and report back Commented Jul 11, 2014 at 12:41
  • Hi guys, thank you for your answers! Can you please tell me which directory to check the errors? I am a bit lost.
    – JasonC91
    Commented Jul 11, 2014 at 19:45

6 Answers 6


If I take a look at the line 104 your error logs are complaining about, I see the following

#File: app/code/core/Mage/Adminhtml/Controller/Action.php
protected function _setActiveMenu($menuPath)
    return $this;

It looks like Magento's trying to grab a reference to the menu block, but it can't became some customization to your system has removed this menu, and then tried to call setActive on a non-object.

$layout = $this->getLayout();
$block  = $layout->getBlock('menu');

So, your first question should be what removed this menu. Possibilities include

  • A custom module
  • Someone's hacked some core code
  • Your admin layout XML files are somehow inaccesible to Magento, and the menu was never added

Based on the rest of your question, and the other errors you're seeing (a missing mage_banners table), it sounds like your best bet may be finding a Magento professional to help get your site repaired. It seems like these issues may be the only the tip of the iceberg.

  • Hi Alan! I greatly appreciate your help. Is the Menu you're referring to the frontend Catalog Menu? I use CustomMenu extension. I am currently transferring most of the pages into a new install, copy and pasting content page by page. I believe this is the best option since I am not familiar with code. Thank you for the help and thorough answer!
    – JasonC91
    Commented Jul 19, 2014 at 21:50

In my case, after updating a testshop installation from to (yes, I know: that's a huge update and trouble was expected), clearing the cache didn't help and as deactivating modules didn't show effects, I stopped there.

Then I found this entry at ukbusinessforums.co.uk and that did the trick for me. So I looked into /app/design/adminhtml/default/default/ and found, that after the update the /etc/ directory was missing! So I downloaded the complete magento suite and uploaded the /adminhtml/default/default/ data and there the login was again! However, obviously, the CSS was missing - so I also uploaded the whole of the /skin/adminhtml/default/default/ contents.

Now, everything is running smoothly again. Hope it helps.


This is the issue after upgrading magento version 1.8 to 1.9.

Magento upgrade unable to download the adminhtml design files.

So means you have to download the latest Magento version or in which Magento version you are upgrading.

After downloading copy all files from to app/design/adminhtml and do this for skin adminhtml also.

May be this will solve your problem.


I found that during the upgrade process the files ending in .phtml under directory :var/www/app/design/adminhtml/default/default/template/xmlconnect/edit/tab/design/preview were actually created as directories, so they were not able to be read properly. Remove them using rm -rf {name of directory}, and perform the upload for adminhtml as suggested by Vinay Sikarwar.


If you have access to the file system try deleting the cache folder in the var folder. Also look in var/log/exception to view the log files.

Try this go to

app/etc/modules/< MODULE_NAME>.xml

and change

< active >true< /active> to < active>false< /active>

for each module until you can get the admin page back. Remember to delete the cache folder in var/cache after each change. I hope this helps.

  • Hi, thank you for the suggestion. I have manually deleted the cache before, but it didn't fix the issue! I do not see a /var/log/exception |||| all i see here is /var/session, /var/report, /var/locks, /var/cache, /var/package,/var/backup, and a 1398366300_db.gz file, and some other files. Please tell me what else I can do or need to figure this out!
    – JasonC91
    Commented Jul 11, 2014 at 22:23
  • Hi, I found a error_log in main directory!
    – JasonC91
    Commented Jul 11, 2014 at 22:34
  • table or view not found: 1146 Table 'statis91_mage2.mage_banners' This is where I would begin looking it seems like you added an extension that didn't properly build out the tables.
    – Egregory
    Commented Jul 14, 2014 at 16:17
  • This error occurred after the initial white page, I believe it was my attempt to fix on GoDaddy, I've reenabled that table on installatron . could you help guide me as to what the fatal error means?
    – JasonC91
    Commented Jul 14, 2014 at 20:06
  • after a quick google this seems like it pertains to this but without knowing if there was an extension installed I'm just shooting in the dark. What happened prior to you getting this error?
    – Egregory
    Commented Jul 14, 2014 at 20:14

@Egregory Your answer solved my problem to make Magento 2.2.0 working.

After upgrading from Magento 2.1.0 to 2.2.0, my admin panel displays same error. After use your solution I am able to found my one of custom module stops working admin panel.

Thank you for your answer.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.