- Issue created by @pameeela
- ๐ฆ๐บAustralia pameeela
- First commit to issue fork.
- Merge request !9469issue 3473241:include a setting for excluding tags and add core to exclude html tags during trim โ (Open) created by annmarysruthy
- Status changed to Needs work
6 months ago 1:42pm 11 September 2024 - ๐ฎ๐ณIndia sriharsha.uppuluri Hyderabad
sriharsha.uppuluri โ made their first commit to this issueโs fork.
- Status changed to Needs review
6 months ago 8:01am 18 September 2024 - ๐ฎ๐ณIndia sriharsha.uppuluri Hyderabad
Fixed the test case failure issue
- Status changed to Needs work
6 months ago 2:58pm 18 September 2024 - ๐บ๐ธUnited States smustgrave
Appears to be missing test cases and upgrade path.
- ๐ฉ๐ชGermany Grevil
Just ran into this while using metatag + glossify.
Glossify provides filters, which automaticall create tooltips / links for words, for which a node or a taxonomy term exists. These links use the linked node body, as the tooltip, which results in a VERY long "title" HTML Tag:
Now, if I would like to use the token [node:summary] inside a metatag or anywhere else, the summary won't be displayed correctly as you can see here:
Now this stems from the same issue, this issue is about. But the current MR doesn't solve it deeply enough. The real root cause of this is the
text_summary()
method from the core "text" module.
In my opinion we should strip the tags there. The method doc says the following:
Generates a trimmed, formatted version of a text field value
I don't think stripping HTML tags would change the documented functionality of this method.
- ๐ฉ๐ชGermany Anybody Porta Westfalica
Thanks, I can also confirm this issue and this is definitely a bug, not a feature request. The expected behaviour is to strip the affected text.
For example, using the Metatag module (which uses [node:summary] by default for node meta descriptions!), this bug will break the metatag generation if the shortened text has a long link in the beginning. The text will be stripped right before the link and that's it.