Magento login admin page FATAL ERROR / WHITE SCREEN Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Fundamentals for debugging a Magento storeWhite screen after updating MagentoCan't Login to Admin after Installing Extensionbefore=“Mage_Adminhtml” after=“Mage_Adminhtml”Blank admin page after successful login for one specific IP address …1.9 admin panel login problemCan't create user or log in to Magento Front End ce 1.9 with ChromeBlank white screen of magento admin after upgradeAdmin page gives 404 error after domain name change“invalid form key. please refresh the page” - cannot login to admin panelCustomer Registration Problem with Magento. Registers Successfully, but doesn't loginWhen I tried to save a Email Template in Admin, it thows me a 404 error: Page not found (only with some values and only in production)
Why are two-digit numbers in Jonathan Swift's "Gulliver's Travels" (1726) written in "German style"?
A journey... into the MIND
Can this water damage be explained by lack of gutters and grading issues?
Is my guitar’s action too high?
When does Bran Stark remember Jamie pushing him?
What were wait-states, and why was it only an issue for PCs?
Why does BitLocker not use RSA?
Raising a bilingual kid. When should we introduce the majority language?
Does using the Inspiration rules for character defects encourage My Guy Syndrome?
Recursive calls to a function - why is the address of the parameter passed to it lowering with each call?
How to get a single big right brace?
What is the ongoing value of the Kanban board to the developers as opposed to management
Does GDPR cover the collection of data by websites that crawl the web and resell user data
What documents does someone with a long-term visa need to travel to another Schengen country?
How to leave only the following strings?
Married in secret, can marital status in passport be changed at a later date?
Why is ArcGIS Pro not symbolizing my entire range of values?
How do I deal with an erroneously large refund?
How to create a command for the "strange m" symbol in latex?
Is Vivien of the Wilds + Wilderness Reclimation a competitive combo?
Weaponising the Grasp-at-a-Distance spell
Unix AIX passing variable and arguments to expect and spawn
Why did Israel vote against lifting the American embargo on Cuba?
Kepler's 3rd law: ratios don't fit data
Magento login admin page FATAL ERROR / WHITE SCREEN
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Fundamentals for debugging a Magento storeWhite screen after updating MagentoCan't Login to Admin after Installing Extensionbefore=“Mage_Adminhtml” after=“Mage_Adminhtml”Blank admin page after successful login for one specific IP address …1.9 admin panel login problemCan't create user or log in to Magento Front End ce 1.9 with ChromeBlank white screen of magento admin after upgradeAdmin page gives 404 error after domain name change“invalid form key. please refresh the page” - cannot login to admin panelCustomer Registration Problem with Magento. Registers Successfully, but doesn't loginWhen I tried to save a Email Template in Admin, it thows me a 404 error: Page not found (only with some values and only in production)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
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.
ERROR LOGS
/Var/Report:
::::::::::::One of the files in /var/report there was an error:::::::::::::
admin login ce-1.9.0.1
|
show 4 more comments
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.
ERROR LOGS
/Var/Report:
::::::::::::One of the files in /var/report there was an error:::::::::::::
admin login ce-1.9.0.1
from your index.php uncomment the line #ini_set('display_errors', 1);
– Pradeep Sanku
Jul 11 '14 at 11:26
Set debugging mode on. Post that fatal error here
– brainReader
Jul 11 '14 at 11:51
Check for PHP memory limit.
– Sukeshini
Jul 11 '14 at 11:55
Check error logs and report back
– Douglas Radburn
Jul 11 '14 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.
– Lykingond
Jul 11 '14 at 19:45
|
show 4 more comments
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.
ERROR LOGS
/Var/Report:
::::::::::::One of the files in /var/report there was an error:::::::::::::
admin login ce-1.9.0.1
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.
ERROR LOGS
/Var/Report:
::::::::::::One of the files in /var/report there was an error:::::::::::::
admin login ce-1.9.0.1
admin login ce-1.9.0.1
edited 4 hours ago
Lykingond
asked Jul 11 '14 at 11:24
LykingondLykingond
1091415
1091415
from your index.php uncomment the line #ini_set('display_errors', 1);
– Pradeep Sanku
Jul 11 '14 at 11:26
Set debugging mode on. Post that fatal error here
– brainReader
Jul 11 '14 at 11:51
Check for PHP memory limit.
– Sukeshini
Jul 11 '14 at 11:55
Check error logs and report back
– Douglas Radburn
Jul 11 '14 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.
– Lykingond
Jul 11 '14 at 19:45
|
show 4 more comments
from your index.php uncomment the line #ini_set('display_errors', 1);
– Pradeep Sanku
Jul 11 '14 at 11:26
Set debugging mode on. Post that fatal error here
– brainReader
Jul 11 '14 at 11:51
Check for PHP memory limit.
– Sukeshini
Jul 11 '14 at 11:55
Check error logs and report back
– Douglas Radburn
Jul 11 '14 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.
– Lykingond
Jul 11 '14 at 19:45
from your index.php uncomment the line #ini_set('display_errors', 1);
– Pradeep Sanku
Jul 11 '14 at 11:26
from your index.php uncomment the line #ini_set('display_errors', 1);
– Pradeep Sanku
Jul 11 '14 at 11:26
Set debugging mode on. Post that fatal error here
– brainReader
Jul 11 '14 at 11:51
Set debugging mode on. Post that fatal error here
– brainReader
Jul 11 '14 at 11:51
Check for PHP memory limit.
– Sukeshini
Jul 11 '14 at 11:55
Check for PHP memory limit.
– Sukeshini
Jul 11 '14 at 11:55
Check error logs and report back
– Douglas Radburn
Jul 11 '14 at 12:41
Check error logs and report back
– Douglas Radburn
Jul 11 '14 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.
– Lykingond
Jul 11 '14 at 19:45
Hi guys, thank you for your answers! Can you please tell me which directory to check the errors? I am a bit lost.
– Lykingond
Jul 11 '14 at 19:45
|
show 4 more comments
6 Answers
6
active
oldest
votes
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)
$this->getLayout()->getBlock('menu')->setActive($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');
$block->setActive($menuPath);
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!
– Lykingond
Jul 19 '14 at 21:50
add a comment |
In my case, after updating a testshop installation from 1.7.0.2
to 1.9.1.0
(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 1.9.1.0
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.
add a comment |
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.
add a comment |
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.
add a comment |
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!
– Lykingond
Jul 11 '14 at 22:23
Hi, I found a error_log in main directory!
– Lykingond
Jul 11 '14 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
Jul 14 '14 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?
– Lykingond
Jul 14 '14 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
Jul 14 '14 at 20:14
|
show 2 more comments
@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.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f28653%2fmagento-login-admin-page-fatal-error-white-screen%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
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)
$this->getLayout()->getBlock('menu')->setActive($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');
$block->setActive($menuPath);
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!
– Lykingond
Jul 19 '14 at 21:50
add a comment |
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)
$this->getLayout()->getBlock('menu')->setActive($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');
$block->setActive($menuPath);
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!
– Lykingond
Jul 19 '14 at 21:50
add a comment |
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)
$this->getLayout()->getBlock('menu')->setActive($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');
$block->setActive($menuPath);
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.
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)
$this->getLayout()->getBlock('menu')->setActive($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');
$block->setActive($menuPath);
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.
edited Feb 6 '16 at 0:43
answered Jul 18 '14 at 21:12
Alan StormAlan Storm
29.3k22120309
29.3k22120309
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!
– Lykingond
Jul 19 '14 at 21:50
add a comment |
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!
– Lykingond
Jul 19 '14 at 21:50
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!
– Lykingond
Jul 19 '14 at 21:50
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!
– Lykingond
Jul 19 '14 at 21:50
add a comment |
In my case, after updating a testshop installation from 1.7.0.2
to 1.9.1.0
(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 1.9.1.0
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.
add a comment |
In my case, after updating a testshop installation from 1.7.0.2
to 1.9.1.0
(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 1.9.1.0
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.
add a comment |
In my case, after updating a testshop installation from 1.7.0.2
to 1.9.1.0
(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 1.9.1.0
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.
In my case, after updating a testshop installation from 1.7.0.2
to 1.9.1.0
(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 1.9.1.0
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.
edited Aug 31 '16 at 13:38
Akif
7761134
7761134
answered Apr 20 '15 at 12:28
JohannesJohannes
9115
9115
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Jan 29 '16 at 16:57
Vinay SikarwarVinay Sikarwar
43239
43239
add a comment |
add a comment |
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.
add a comment |
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.
add a comment |
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.
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.
answered Feb 5 '16 at 23:20
Stevan VeselinovicStevan Veselinovic
211
211
add a comment |
add a comment |
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!
– Lykingond
Jul 11 '14 at 22:23
Hi, I found a error_log in main directory!
– Lykingond
Jul 11 '14 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
Jul 14 '14 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?
– Lykingond
Jul 14 '14 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
Jul 14 '14 at 20:14
|
show 2 more comments
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!
– Lykingond
Jul 11 '14 at 22:23
Hi, I found a error_log in main directory!
– Lykingond
Jul 11 '14 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
Jul 14 '14 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?
– Lykingond
Jul 14 '14 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
Jul 14 '14 at 20:14
|
show 2 more comments
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.
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.
edited Jul 18 '14 at 20:33
answered Jul 11 '14 at 20:48
EgregoryEgregory
4092416
4092416
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!
– Lykingond
Jul 11 '14 at 22:23
Hi, I found a error_log in main directory!
– Lykingond
Jul 11 '14 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
Jul 14 '14 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?
– Lykingond
Jul 14 '14 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
Jul 14 '14 at 20:14
|
show 2 more comments
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!
– Lykingond
Jul 11 '14 at 22:23
Hi, I found a error_log in main directory!
– Lykingond
Jul 11 '14 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
Jul 14 '14 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?
– Lykingond
Jul 14 '14 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
Jul 14 '14 at 20:14
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!
– Lykingond
Jul 11 '14 at 22:23
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!
– Lykingond
Jul 11 '14 at 22:23
Hi, I found a error_log in main directory!
– Lykingond
Jul 11 '14 at 22:34
Hi, I found a error_log in main directory!
– Lykingond
Jul 11 '14 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
Jul 14 '14 at 16:17
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
Jul 14 '14 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?
– Lykingond
Jul 14 '14 at 20:06
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?
– Lykingond
Jul 14 '14 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
Jul 14 '14 at 20:14
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
Jul 14 '14 at 20:14
|
show 2 more comments
@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.
add a comment |
@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.
add a comment |
@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.
@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.
answered Oct 29 '17 at 15:19
P_UP_U
714518
714518
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f28653%2fmagento-login-admin-page-fatal-error-white-screen%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
from your index.php uncomment the line #ini_set('display_errors', 1);
– Pradeep Sanku
Jul 11 '14 at 11:26
Set debugging mode on. Post that fatal error here
– brainReader
Jul 11 '14 at 11:51
Check for PHP memory limit.
– Sukeshini
Jul 11 '14 at 11:55
Check error logs and report back
– Douglas Radburn
Jul 11 '14 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.
– Lykingond
Jul 11 '14 at 19:45