{"id":34709,"date":"2024-12-09T14:30:52","date_gmt":"2024-12-09T09:30:52","guid":{"rendered":"https:\/\/devrims.com\/?p=34709"},"modified":"2025-03-24T15:42:18","modified_gmt":"2025-03-24T10:42:18","slug":"debug-magento-2-store","status":"publish","type":"post","link":"https:\/\/devrims.com\/blog\/debug-magento-2-store\/","title":{"rendered":"How To Debug Magento 2 Store – Easy Steps"},"content":{"rendered":"\r\n\r\n\r\n\r\n\r\n\r\n\n

This blog covers the actual quick methods for Magento 2 debugging.<\/p>\n\n\n\n

Debugging is an essential part of every development project or eCommerce store. Every Developer knows how necessary it is to debug the Magento 2 store when needed.<\/p>\n\n\n\n

Magento 2 is a newer version of Magento; debugging Magento 2 is slightly different from Magento 1. For a developer, it is crucial to learn about it because Magento’s market share has increased from 9% to 13%<\/a> in just the last year!<\/p>\n\n\n\n

For a breakdown of Magento 1 and Magento 2, read our blog on which Magento version you should choose<\/a>.<\/p>\n\n\n\n

There are multiple methods used to debug code in a Magento 2 Store. In this article, I will show you some of the best Magento debugging methods so you can conveniently use the Magento 2 eCommerce store.<\/p>\n\n\n\n

Why Do You Need to Debug Magento 2 Store?<\/h2>\n\n\n\n
\"Why<\/figure>\n\n\n\n

Debugging is the testing framework; it will help you identify the bugs in your Magento eCommerce store. It will also assist you in resolving bugs\/errors or abnormalities in computer programs.<\/p>\n\n\n\n

Type of Development Mode in Magento 2 Debugging<\/h2>\n\n\n\n
\"Type<\/figure>\n\n\n\n

Before going through the methods of debugging Magento 2, you need to understand the types of development modes. There are three types of development modes: Default, Developer, and Production mode\u2014Let’s discuss each of them one by one:<\/p>\n\n\n\n

1- Default mode<\/h3>\n\n\n\n

If no other mode is enabled, the default mode is \u201cthe default mode\u201d with no amendments, changes, editing, personalization, or additions. This mode allows the following things:<\/p>\n\n\n\n

    \n
  • The error is not displayed to the visitors when using default mode and is stored in log files.<\/li>\n\n\n\n
  • The static files are published to the pub\/static record to make them faster.<\/li>\n\n\n\n
  • The static file is dynamically generated in response to a request.<\/li>\n<\/ul>\n\n\n\n

    2- Developer Mode<\/h3>\n\n\n\n

    The developer mode is used for development. It includes the following:<\/p>\n\n\n\n

      \n
    • The static files are published to the pub\/static record (as in the default mode). With that, they are always generated from basic templates.<\/li>\n\n\n\n
    • Users can see the errors. It is displayed in the browser.<\/li>\n\n\n\n
    • Errors that get in var\/reports<\/strong> are more detailed.<\/li>\n<\/ul>\n\n\n\n

      3- Production mode<\/h3>\n\n\n\n

      Production mode is one of the best modes. It is fully optimized and suitable for server production. The production mode offers all data that will be loaded from the cache.<\/p>\n\n\n\n

      This mode allows the following things:<\/p>\n\n\n\n

        \n
      • The errors will not display in the log files<\/li>\n\n\n\n
      • The static files are displayed only in the cache.<\/li>\n<\/ul>\n\n\n\n

        To change the developer mode’s production mode, you must navigate bin\/Magento starting with settings deploy:mode: set Developer<\/strong>.<\/p>\n\n\n\n

        After that, you need to delete the content of the directories that we mention below:<\/p>\n\n\n\n

        \/*Code Start\/*
        var\/cache
        var\/di
        var\/generation
        var\/view_preprocessed
        pub\/static
        \/*Code End\/*<\/pre>\n\n\n\n
        Note:<\/strong> Do not delete the .htaccess file and the pub\/static\/deployed_version.txt<\/strong> file.<\/em><\/p>\n\n\n\n
        Best Methods of Debugging Magento 2 Store<\/h2>\n\n\n\n
        \"Methods<\/figure>\n\n\n\n
        I have mentioned some of the best methods to check out and debug your Magento 2 eCommerce store. Let\u2019s see how each method can make your Magento 2 store faster and wiser.<\/p>\n\n\n\n
        Xdebug and PhpStorm Combination<\/h3>\n\n\n\n
        \"Xdebug<\/figure>\n\n\n\n
        Xdebug and PhpStorm are both great combinations for debugging Magento 2. The main benefit of the method is the breakpoints installation process, and it can assist the Developer in reviewing and changing variables at any time<\/p>\n\n\n\n
        Magento 2 Developer mode<\/h3>\n\n\n\n
        Magento developer mode shows the errors on your browser screen. If you want to enable this mode, you need to add the following code line in the directory using the console:<\/p>\n\n\n\n
        php bin\/magento deploy:mode:set developer<\/pre>\n\n\n\n
        Enable ‘Template Path Hints<\/h3>\n\n\n\n
        The template path hints method shows the names of all page blocks and classes. To enable the template path, you need to do the following steps:<\/p>\n\n\n\n
          \n
        • Login into your Magento 2 store<\/li>\n\n\n\n
        • Next, navigate the store configuration<\/li>\n\n\n\n
        • Next, go to the Advanced section and click on the Developer<\/li>\n\n\n\n
        • Next, extend Debug from the menu and set Enabled Template Path Hints for Storefront<\/li>\n\n\n\n
        • Next, enable Template Path Hints for Admin and Add Block Names to Hints to YES.<\/li>\n<\/ul>\n\n\n\n
          Enable Magento 2 Display Errors<\/h3>\n\n\n\n
          Magento 2 does not show the display error on the screen. However, if you want to show this error, you must rename the local.xml.The sample<\/strong> file was placed in pub\/errors<\/strong> to local.xml<\/strong>.<\/p>\n\n\n\n
          The content of local.xml.sample:<\/p>\n\n\n\n
          <?xml version=\"1.0\"?>
          <!--
          \/**
          * Copyright \u00a9 Magento, Inc. All rights reserved.
          * See COPYING.txt for license details.
          *\/
          -->
          <config>
          <skin>default<\/skin>
          <report>
          <!--
          \"action\" can be set to \"print\" to show exception on screen and \"email\"
          to send exception on specified email
          -->
          <action>print<\/action>
          <!--
          in \"subject\" you can set subject of email
          -->
          <subject>Store Debug Information<\/subject>
          <!--
          \"email_address\" admin email address
          -->
          <email_address><\/email_address>
          <!--
          \"trash\" is handle about trace info
          value \"leave\" is for store on disk
          value \"delete\" is for cleaning
          -->
          <trash>leave<\/trash>
          <\/report>
          <\/config><\/pre>\n\n\n\n
          Magento 2 Logs<\/h3>\n\n\n\n
          This method is hidden from the user and doesn’t require data display on the screen. Furthermore, in Magento 2, the PsrLogLoggerInterface class provides logging events and output variables to Magento log files. <\/p>\n\n\n\n
          Following are the public methods that you can see:<\/p>\n\n\n\n
          emergency($message, array $context = array())
          alert($message, array $context = array())
          critical($message, array $context = array())
          error($message, array $context = array())
          warning($message, array $context = array())
          notice($message, array $context = array())
          info($message, array $context = array())
          debug($message, array $context = array())
          log($level, $message, array $context = array())<\/pre>\n\n\n\n
          Frequently Asked Questions<\/h2>\n\n\n\n
          Here are answers to some frequently asked questions.<\/p>\n\n\n