Feature #70461
closed
Some entities should be possible to enter and output
0%
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.
Updated by
Updated by Riccardo De Contardi about 7 years ago
- Related to Bug #80285: RTE: soft hyphens are visible in IE11 in text mode and encoded added
Updated by Riccardo De Contardi about 7 years ago
- Related to Feature #77848: Make soft hyphens visible backend forms added
Updated by Riccardo De Contardi about 7 years ago
- Category set to Backend User Interface
Updated by Susanne Moog over 1 year ago
If you need this feature, you can use https://github.com/WapplerSystems/Shyguy/ as long as there is no core provided solution.
Updated by Ayke Halder about 1 year ago
ยท Edited
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-rules
https://gist.github.com/rr-it/223d32f8b3abe8800a599178a535b8c8
Updated by Georg Ringer 7 months ago
- Status changed from New to Rejected
Hey 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!