The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.To reproduce the bug,
Create a view
In the Header/Footer section, add a Global Unfiltered Text area
Place markup to create a Button (aka tag) in the area.
See Preview or save and find view elsewhere
It's expected that the verbiage is either corrected or that this area handler is corrected to allow unfiltered markup.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | views_2.PNG | 31.81 KB | gnanagowthaman sankar |
| #7 | views_1.PNG | 41.38 KB | gnanagowthaman sankar |
| 2016-01-26_20:13:25-Selection.png | 112.2 KB | generalredneck | |
| #7 | views_4.PNG | 43.64 KB | gnanagowthaman sankar |
| #7 | views_3.PNG | 46.73 KB | gnanagowthaman sankar |
Comments
Comment #2
eightygrit commentedDitto.
Comment #3
markdcDouble ditto.
Comment #4
jcmartinezThis still happens with Drupal 8.8.5 and tokens.
To reproduce:
1 - Create a user based view.
2 - Add field User: User ID [hidden]
3 - Add to Header or Footer: Global: Unfiltered text
4 - Within content add:
<a href="/user/{{ uid }}/edit?destination=/dashboard">Edit account</a>This part of the view will render as:
The expectation is that it would render as:
Things that I have tried:
I tested without a token. This works, but it's not what I need:
<a href="/user/1/edit?destination=/dashboard">Edit account</a>Workaround:
I ended up building the link by rewriting a field in the field area of the view which does the token replacements and doesn't remove HTML.
Comment #5
gnanagowthaman sankar commentedComment #6
jcmartinezComment #7
gnanagowthaman sankar commentedHi @jcmartinez,
I cannot able to replicate the issue on my localsite. Can you please guide if am wrong. I am attaching the working screenshots.
Thanks & Regards,
Gnanagowthaman Sankar
Comment #8
gnanagowthaman sankar commentedComment #9
gnanagowthaman sankar commentedSorry for the adding more comments i had change the version no
Comment #10
himanshu_sindhwani commentedComment #11
himanshu_sindhwani commentedThe unfiltered text is filtered using Xss::filterAdmin(), therefore only certain tags are allowed like in the custom text field. I have updated the description of the filtered text and added a help text which makes it more clear while using HTML in content. Closing this issue as a duplicate. Follow the trail here Wrapper gets removed while adding html textfield or textarea using replacement patterns
Comment #12
jcmartinezThis issue was created in 2016.
You shouldn't set the exact same issue created a few months ago as the parent. Lot's of people have provided feedback on this issue and their contribution shouldn't be ignored.
I'm setting this as a related issue, even though https://www.drupal.org/project/drupal/issues/3136107 is actually the duplicate, because the duplicate has a patch.
Comment #13
himanshu_sindhwani commentedYes, you are right the contributions shouldn't be ignored.
A couple of things I noticed before marking this as closed and a child issue:
Therefore I uploaded the patch to the newer issues and asked for the feedbacks.