Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.In the paragraph summary (using the experimental widget) HTML entities such as are printed. I would expect them to just render as normal white spaces.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | After patch .png | 39.77 KB | deepalij |
| #6 | before patch - html entities .png | 40.51 KB | deepalij |
| #5 | paragraphs-summary_html_entities-3160709-5.patch | 653 bytes | falc0 |
Comments
Comment #2
rp7 commentedComment #3
rp7 commentedPatch attached fixes the issue on my side. It first does a html_entity_decode() before using htmlspecialchars() again.
Comment #4
rp7 commentedComment #5
falc0 commentedUpdated patch so it applies to the current version.
Comment #6
deepalij commentedApplied patch #5 on Drupal 10.1.x-dev
Patch applied cleanly
Able to reproduce the issue
HTML entities issue got fixed after applying the patch
Before patch:
After patch:
RTBC+1
Comment #7
pivica commentedWe have the same problem and first I created a patch and then checked for existing issue. A bit different approach, doing decoding in template_preprocess_paragraphs_summary() function. I am not really sure which approach is better, it feels that doing it in preprocessor is a more general approach?
Thinking about spaces, if we have two or more spaces connected should we replace them with one space?
Comment #8
pivica commentedDiscussed with @Berdir and he prefers approach in #5, dropping mine patch and testing against #5.
Comment #9
berdirCommitted.