trying to create a custom theme with bitnami XAMPP using magento devdocs
https://devdocs.magento.com/guides/v2.2/frontend-dev-guide/themes/theme-create.html
I get this error when I try to access the admin panel
There has been an error processing your request
Exception printing is disabled by default for security reasons.
Error log record number: 1130478184
I think you have to first check in your error log number "1130478184" where you exactly know what is the issue. I think from your given link which you refer your issue must be occured from theme.xml file's <preview_image>media/preview.jpg</preview_image> line. You have to try with comment following code in theme.xml file:-
<!--media>
<preview_image>media/preview.jpg</preview_image>
</media-->
Am getting below error before installing magento could any one help me on this
There has been an error processing your request
Exception printing is disabled by default for security reasons.
Error log record number: 67392566
Go to var/report and open file with this number 67392566 and see the exact error then send me so I can help you exactly with your query.
I just re-installed Magento and restored the old database with PhpMyAdmin.
The front page of the website is OK. But in the backend I've got this error when I go to Manage Categories.
Exception printing is disabled by default for security reasons.
Error log record number: 986836145855
Does anyone know how to solve this problem?
Go to magento/var/report and open the file with the Error log record number name (986836145855 in your case).
In that file you can find the complete description of the error.
For log files like system.log and exception.log, go to magento/var/log/.
i have a serious problem in Magento Admin Backend. After login its shows a BLANK Page. i used the same files and database in different server, there it was working fine but when i have transferred files into LIVE then Admin issues came. Please help me over this as i got frustrated from last some dayz. If you need any more dertails then plz ask but i need to resolve this soon. Link: http://studywings.com/index.php/admin/
Magento ver: 1.7
flush your magento root /var/cache folder and /var/session folders, It may have previous server session that may cause problems.
Otherwise disable all third party modules and try again. I think this will help
I had the Same problem,
i have also debug the any errors occured, i tried index.php file
ini_set('display_errors', 1);
error_reporting(E_ALL);
$_SERVER['MAGE_IS_DEVELOPER_MODE'] = true;
pleced above code in index.php file. after that i have tried admin login.
showing the errors are session related, header already send errors.
i have to add the code in root/index.php file in top add the following line.
ob_start();
after that tried the login its worked.
Cheers..!
Is url changes to this after click login button or not?
http://yourdomain.com/index.php/admin/index/index/key/(key value)/
if url changes but not not show the dashboard page then go to
app/code/core/Mage/Core/Model/Session/Abstract/Varien.php
make copy of this file
Find the code for setting session cookie parameters these started on line 77
Comment out the final three lines and be sure to remove the comma after $this->getCookie()->getPath(). You should end up with this:
// set session cookie params
session_set_cookie_params(
$this->getCookie()->getLifetime(),
$this->getCookie()->getPath()
// $this->getCookie()->getDomain(),
// $this->getCookie()->isSecure(),
// $this->getCookie()->getHttponly()
also line 104 comment out :
//call_user_func_array('session_set_cookie_params', $cookieParams);
If there is no change in url after click login then try to uncomment display error and see error_log file of your server
I think this problem is due to file permissions. As you added files from one server to another, permissions might be get changed.. Try to give the permissions to all the files. Check this http://www.mage-shop.com/forum/threads/3-Magento-Admin-Backend-Blank-Page-Error
There are a number of things that can cause it, but it's most common after migrating to a new server, last time it happened to me it was an excessively low php memory_limit setting on the new server - the Admin part of the site uses a lot more resources per user than the frontend.
In general when having this issue:
Flush out your cache by emptying var/cache
Clear out sessions by emptying var/sessions
Check the magento error logs/reports for an error code in var\logs and var/reports
Turn on magento error logs in mysql if logging isn't already on! (look in core_config_data for WHERE path like 'dev/log/active'
Check if your php configuration is displaying errors
Check your apache/php error logs for more clues - memory errors will show up here for example
Try this solution
It sounds like you want to enable Developer mode. Add this to your .htaccess file:
SetEnv MAGE_IS_DEVELOPER_MODE "true"
You may also want to enable display errors in index.php:
ini_set('display_errors', 1);
The best way I have found to debug is with X-Debug in a local environment. You can also use log files to help debug in a production environment, if your unable to run X-Debug in the environment.
I've got a more detailed posting here:
http://www.molotovbliss.com/debugging-tips-and-tricks-with-magento-commerce
Consider also installing XDebug
Hope this helps you!
Just to complete the other answers....
I am upgrading a magento install, and got the same problem, in the end I had another folder inside of var/
magento/var/minifycache
Only worked after clear deleting the files inside of this folder.
I had the same problem after uninstalling an extension. I thought that clearing cache would be enough, and I did without success... later speaking with the technical team, they commented me that it did not work because I hace memcache installed, and needed to be done the cleaning via system - backend (that i coudl not see...)
When a user logs in to the front end incorrectly, they get a 500 error page.
In previous installations, the page just refreshes. Ideally, I'd like an error message displayed but this isn't happening either (even on previous installations). I assumed that this was achieved by:
<jdoc:include type="message" />
Paths to log/tmp files are correct. Permissions seem OK. Any ideas?
Thanks,
Andy
I thought it was something with the logs dir. Change the permissions and try again.
Update the configuration file
update the full URL of temp and log folder