#70461Some entities should be possible to enter and output
Description
Since 6.2 fields that are editable in the backend get htmlSpecialChars while rendering.
Without disableling this htmlSpecialChars its not possible to let editors take usage of
­
because the & gets encoded.
A solution is needed to make this possible.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 2
History 8
-
Daniel Goerz changed description 01/10/16, 21:59
-
Daniel Goerz changed description 01/10/16, 22:00
-
Riccardo De Contardi changed Related to #80285 10/29/17, 11:55
-
Riccardo De Contardi changed Related to #77848 10/29/17, 11:55
-
Riccardo De Contardi changed category 10/29/17, 11:56
-
Susanne Moog commented 07/07/23, 10:19
-
Ayke Halder commented 11/21/23, 15:22
Just asking before I put time into this:
Is this more a ‘nitpick’ or does a solution for “visible SHY/soft-hyphens in the TYPO3-backend” gets accepted into core?> * Is the issue itself relevant?
> * Does the solution embed well in current development strategies?
> * Is the architectural solution ok or is the patch just fixing some symptom instead of a different, maybe bigger problem?
> * Does the solution contradict other patches we have in the same area?Check out this approach via TCA custom eval-rule:
https://docs.typo3.org/m/typo3/reference-tca/11.5/en-us/ColumnsConfig/Type/Input/Properties/Eval.html#custom-eval-ruleshttps://gist.github.com/rr-it/223d32f8b3abe8800a599178a535b8c8
-
Georg Ringer commented and changed status
NewRejected 06/23/24, 12:29Hey Sebastian,
default escaping is used since a long time – especially since using fluid – and required to have a secured output.
as there are ckeditor plugins to include a soft hyphen, I am closing this issue.if you don’t agree, feel free to contact me via slack!
If you need this feature, you can use https://github.com/WapplerSystems/Shyguy/ as long as there is no core provided solution.