CoderFunda
  • Home
  • About us
    • Contact Us
    • Disclaimer
    • Privacy Policy
    • About us
  • Home
  • Php
  • HTML
  • CSS
  • JavaScript
    • JavaScript
    • Jquery
    • JqueryUI
    • Stock
  • SQL
  • Vue.Js
  • Python
  • Wordpress
  • C++
    • C++
    • C
  • Laravel
    • Laravel
      • Overview
      • Namespaces
      • Middleware
      • Routing
      • Configuration
      • Application Structure
      • Installation
    • Overview
  • DBMS
    • DBMS
      • PL/SQL
      • SQLite
      • MongoDB
      • Cassandra
      • MySQL
      • Oracle
      • CouchDB
      • Neo4j
      • DB2
      • Quiz
    • Overview
  • Entertainment
    • TV Series Update
    • Movie Review
    • Movie Review
  • More
    • Vue. Js
    • Php Question
    • Php Interview Question
    • Laravel Interview Question
    • SQL Interview Question
    • IAS Interview Question
    • PCS Interview Question
    • Technology
    • Other

23 February, 2022

Magento 2 Display Error Enable Error Reporting

 Programing Coderfunda     February 23, 2022     Magento 2, MAGENTO TUTORIALS     No comments   

 

Magento 2 Display Error Enable Error Reporting

This tutorial shows you how to enable error reporting in Magento 2.

In Magento 2, sometimes you’ll encounter a problem in which a black page or a plain white page appears with the error numbers like Error log record number: 568837792838 or any broken content error.

In the default setting of Magento 2, the function which allows displaying the error on the frontend is disabled. Therefore, in today’s post, I will guide you on how to display the error message or enable error reporting on Magento 2.

How to display error: Enable error reporting

  • Method 1: Rename pub/errors/local.xml.sample file
  • Method 2: Edit .htaccess file
  • Method 3: Edit app/bootstrap.php file

Method 1: Rename pub/errors/local.xml.sample file

To display the error on the browser, you can simply rename a one XML file. However, this method is not recommended if you are in the production environment, so you should only consider using this for the development environment. Here is how you do it:

  • Firstly, go to your Magento2 root directory.
  • Then, open pub/errors.
  • After you have opened it, you will see a file whose name is local.xml.sample.
  • Rename it from local.xml.sample to local.xml. In other words, you remove the sample from the file’s name.
  • Finally, go to System > Tools > Cache Management to refresh Cache from the Magento Admin.

Method 2: Edit .htaccess file

The second method to display the error is to edit the .htaccess file of your Magento 2 site. When editing the file you will be able to enable the development mode of Magento as well as the PHP’s error display settings.

Firstly, open the file .htaccess and write the following code at the end of that file:

php_value display_errors on ## enable PHP's error display settings
php_value error_reporting -1 ## set error display to E_ALL

After adding the code, open terminal/command-prompt and access the root directory of your Magento.

cd /path/to/your/magento/directory

Now, run the below command to activate the developer mode.

php bin/magento deploy:mode:set developer

The current deploy mode can be checked with this command:

php bin/magento deploy:mode:show

Finally, clear the Cache with the following command:

php bin/magento cache:clean

After following all the steps above correctly, you will see the error displays on the browser itself when browsing your Magento website. However, just like the first method, this is only good for the development environment.

Method 3: Edit app/bootstrap.php file

Besides editing .htaccess file which is the preferred way to enable error display on your Magento site, you can also edit the PHP file. To edit the file, follow the steps below:

  • Firstly, access your Magento’s root directory.
  • Then, open the file app/bootstrap.php .
  • At the beginning of the file, you will see this line code:
    #ini_set('display_errors', 1);
    

    Once you saw it, please update the code to:

error_reporting(E_ALL); # Set Error Reporting as E_ALL (Report all PHP errors)
ini_set('display_errors', 1); # Un-commenting this line to enable PHP error display

After updating the code, open terminal/command-prompt and then go to the root directory of your Magento.

cd /path/to/your/magento/directory

Then, to enable the developer mode, the following command needs to be run

php bin/magento deploy:mode:set developer

In case you want to check the current deploy mode, you can use the below line:

php bin/magento deploy:mode:show

Finally, clear the Cache:

php bin/magento cache:clean

That’s it. After following all the steps above correctly, you will be able to see error displays on the browser.


  • Share This:  
  •  Facebook
  •  Twitter
  •  Google+
  •  Stumble
  •  Digg
Email ThisBlogThis!Share to XShare to Facebook
Newer Post Older Post Home

0 comments:

Post a Comment

Thanks

Meta

Popular Posts

  • Spring Security PreAuthorize using multi-value enum
    I have a annotation that is declared as follows. @Retention(RetentionPolicy.RUNTIME) @Target(ElementType.METHOD) @PreAuthorize("hasA...
  • Running PHPStan on max with Laravel
      Over the last few years static analysis in PHP, and more specifically Laravel, has become more and more popular. With more people adopting...
  • Generalization
    Generalization Generalization is like a bottom-up approach in which two or more entities of lower-level levels combine to form a higher-leve...
  • Your requirements could not be resolved to an installable set of packages.
    Problems : Your requirements could not be resolved to an installable set of packages. Solution :  Run this command: composer install --ignor...
  • Vue.js Events
      In Vue.js, Events are used to respond to an action. Suppose, you have to build a dynamic website using Vue.js then you'll most likely ...

Categories

  • Ajax (26)
  • Bootstrap (30)
  • DBMS (42)
  • HTML (12)
  • HTML5 (45)
  • JavaScript (10)
  • Jquery (34)
  • Jquery UI (2)
  • JqueryUI (32)
  • Laravel (1017)
  • Laravel Tutorials (23)
  • Laravel-Question (6)
  • Magento (9)
  • Magento 2 (95)
  • MariaDB (1)
  • MySql Tutorial (2)
  • PHP-Interview-Questions (3)
  • Php Question (13)
  • Python (36)
  • RDBMS (13)
  • SQL Tutorial (79)
  • Vue.js Tutorial (69)
  • Wordpress (150)
  • Wordpress Theme (3)
  • codeigniter (108)
  • oops (4)
  • php (853)

Social Media Links

  • Follow on Twitter
  • Like on Facebook
  • Subscribe on Youtube
  • Follow on Instagram

Pages

  • Home
  • Contact Us
  • Privacy Policy
  • About us

Blog Archive

  • July (4)
  • September (100)
  • August (50)
  • July (56)
  • June (46)
  • May (59)
  • April (50)
  • March (60)
  • February (42)
  • January (53)
  • December (58)
  • November (61)
  • October (39)
  • September (36)
  • August (36)
  • July (34)
  • June (34)
  • May (36)
  • April (29)
  • March (82)
  • February (1)
  • January (8)
  • December (14)
  • November (41)
  • October (13)
  • September (5)
  • August (48)
  • July (9)
  • June (6)
  • May (119)
  • April (259)
  • March (122)
  • February (368)
  • January (33)
  • October (2)
  • July (11)
  • June (29)
  • May (25)
  • April (168)
  • March (93)
  • February (60)
  • January (28)
  • December (195)
  • November (24)
  • October (40)
  • September (55)
  • August (6)
  • July (48)
  • May (2)
  • January (2)
  • July (6)
  • June (6)
  • February (17)
  • January (69)
  • December (122)
  • November (56)
  • October (92)
  • September (76)
  • August (6)

Loading...

Laravel News

Loading...

Copyright © CoderFunda | Powered by Blogger
Design by Coderfunda | Blogger Theme by Coderfunda | Distributed By Coderfunda