- First commit to issue fork.
- Merge request !3Issue #3183680: Fix usage of unprocessed text and truncated HTML entities → (Open) created by matthijs
- Open on Drupal.org →Core: 10.1.4 + Environment: PHP 7.3 & MySQL 8last update
12 months ago Waiting for branch to pass - Open on Drupal.org →Core: 10.1.4 + Environment: PHP 7.3 & MySQL 8last update
12 months ago Waiting for branch to pass - Status changed to Needs review
12 months ago 3:04pm 6 December 2023 - 🇧🇪Belgium matthijs
I created an MR that uses the processed text and truncates the HTML without removing/breaking HTML tags or entities.
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 7.3 & MySQL 8last update
8 months ago Waiting for branch to pass - 🇧🇪Belgium keszthelyi Brussels
@Matthijs I tested your MR on our project and so far it's working great, thank you! I need a fixed patch file because of our CI pipeline, so I upload a patch version from it (at commit d144a36e).
Currently, the module is not handling processed text correctly IMO, and this seems to have security implications also in certain cases, besides not applying the formatting. I'm planning to report that separately, but I will reference this issue (and your MR) as a possible solution.
- Open on Drupal.org →Core: 10.2.1 + Environment: PHP 7.3 & MySQL 8last update
8 months ago Waiting for branch to pass - 🇧🇪Belgium keszthelyi Brussels
This patch is almost identical to #8 which is created from @Matthijs' MR. The only difference is that I added support for plain text fields (to handle cases when the processed property is empty for the field).