Bobcares

Enable Debugging in Twig Templates

by | May 18, 2023

 Let us take learn how to Enable Debugging in Twig Templates with the support of our Drupal support services at Bobcares.

Enable Debugging in Twig Templates?

Enable Debugging in Twig Templates

Twig is a contemporary, quick, and secure template framework that assists developers in creating new templates and successfully changing old templates.

There are several distinctions between PHP templates and Twig. Twig has its own set of grammar and coding conventions.

The debugging is significantly easier to enable with Drupal 8. Twig debugging makes it easier for developers to identify template names.

The theme_suggestions hook allows them to build new template naming systems. In the sites/default directory, every Drupal 8 site has a default.services.yml file. Change the name to services.yml.

There is a twig.config argument in that services.yml file. Change the debug value from false to true, but leave the auto_reload and cache variables at false. Save the work and clear the cache.

How to Enable Twig Debugging?

There are several methods or choices for enabling twig theme debugging. This is the most basic way.

Follow the steps below in order to enable twig template debugging by making modifications to services.yml:

  1. Firstly go to the /sites/default folder.
  2. Rename the default.services.yml file to services.yml.
  3. Locate ‘twig.config’ in the services.yml file.
  4. Debug should be set to true.
  5. Head to the sites folder as the next step to enable Debugging in Twig Templates
  6. After that, we have to open the development.services.yml file. In the file type in the following code:

    twig.config:
    debug: true
    auto_reload: true
    cache: false

  7. Make a duplicate of the example.settings.local.php file and rename it settings.local.php.
  8. Uncomment the commandine given below:

    $settings['cache']['bins']['render'] = 'cache.backend.null';

  9. Locate the following code block in the settings.php file.

    if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
    include $app_root . '/' . $site_path . '/settings.local.php';
    }

  10. Paste the command line at the bottom of the file.
  11. Finally, we have to clear the cache to complete the whole process.

Examine the browser’s inspector to view all of the available template recommendations in the code, as well as which templates are currently being utilized.

Enabling Twig Debugging With Drupal Console

If we use the Drupal console, we can carry out all of this with a single command

drupal site:mode dev
However, before uploading the site, remember to re-enable production settings:

drupal site:mode prod

We have to do this before uploading the site to the server.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now seen how to Enable Debugging in Twig Templates with the support of our tech support team.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF