Twig Debug output shows in Group By title if grouping term has a label

Created on 23 August 2019, over 5 years ago
Updated 1 February 2023, about 2 years ago

If Twig Debug is active and I have a Group By field in my view, if I have a label, it shows the Twig Debug output. If I remove the label, it displays as expected.

Without a label

With a label

------

I feel like I've seen another issue related to labels and Twig Debug output being exposed, but I can't find it.

🐛 Bug report
Status

Closed: cannot reproduce

Version

9.5

Component
Views 

Last updated about 1 hour ago

Created by

🇺🇸United States ergophobe

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • 🇳🇿New Zealand quietone

    Just over a year ago steps to reproduce this were ask for and none have been supplied. I have attempted to reproduce the problem on Drupal 10.1.x, umami install, with a duplicate of the content view. I have added a group by field with a label and without. I have checked the twig debug output with each change and I am not able to reproduce the problem.

    The IS suggests that a duplicate exists but I could not find one.

    Since we need steps to reproduce, starting from Drupal install, and none have been provided and I haven't been able to reproduce this I am closing this as cannot reproduce.

    If you encounter this problem, re-open the issue and add steps to reproduce.

    Thanks.

  • Please reopen - this happens on 10.3 and 10.4 for sure -
    1. have theme debug on
    2. make a view with fields
    3. in unformatted list setting select the title field, make sure remove tags in rendered output is off

    Click apply,

    If the unformatted list setting has remove tags in rendered out on - the twig stuff goes away, but the grouped fields do not have links.

  • 🇳🇿New Zealand quietone

    OK. Drupal 10.4 is a maintenance release and receives a limited set of changes.

    So, any change for this will be made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies .

  • 🇮🇳India niranjan_panem Gurugram

    I'm not able to reproduce the issue on drupal 11 clean install.

  • 🇺🇸United States bnjmnm Ann Arbor, MI

    I was just able to reproduce it in 11.x using the steps described in #12

    @niranjan_panem I have reopened multiple legitimate issues today that you had closed due to incorrectly identifying them as no longer occurring. This hurts the project. If you'd like some mentorship regarding how to better do this, please join Drupal Slack (I could not find you there otherwise I would have pinged this to you there), and you can get some mentoring on this.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹

    It could also be better to leave the task to close the issue to somebody else.

Production build 0.71.5 2024