Prevent template files from being rendered when not necessary.

Created on 10 February 2013, about 12 years ago

Updated 17 March 2025, 20 days ago

Problem/Motivation

We have many template files that start with logic that, if fails, will prevent anything from being printed at all. It would be smarter if we could prevent these template files from being rendered at all when not necessary.

For example, theme_comment_post_forbidden turns into the following twig file:

{% if logged_out and can_post_comments %}
  {% if user_register %}
    {% set args = {'@login': user_login_url, '@register': user_register_url} %}
    {{ '<a href="@login">Log in</a> or <a href="@register">register</a> to post comments' | t(args) }}
  {% else %}
    {% set args = {'@login': user_login_url} %}
    {{ '<a href="@login">Log in</a> to post comments' | t(args) }}
  {% endif %}
{% endif %}

Proposed resolution

We should think about whether we should find a way to allow Twig/the theme system to skip the rendering of a template when these conditions are not met.

Some possible candidates:

(Click View source to see the template code)

Remaining tasks

TBD

User interface changes

none.

API changes

TBD

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

theme system

Created by

🇺🇸United States jenlampton

Live updates comments and jobs are added and updated live.

Twig

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 20 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024