Project

General

Profile

Actions

Feature #70461

open

Some entities should be possible to enter and output

Added by Sebastian Fischer over 8 years ago. Updated 5 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2015-10-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

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.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #80285: RTE: soft hyphens are visible in IE11 in text mode and encodedClosed2017-03-15

Actions
Related to TYPO3 Core - Feature #77848: Make soft hyphens visible backend formsClosed2016-09-05

Actions
Actions #1

Updated by Daniel Goerz over 8 years ago

  • Description updated (diff)
Actions #2

Updated by Daniel Goerz over 8 years ago

  • Description updated (diff)
Actions #3

Updated by Riccardo De Contardi over 6 years ago

  • Related to Bug #80285: RTE: soft hyphens are visible in IE11 in text mode and encoded added
Actions #4

Updated by Riccardo De Contardi over 6 years ago

  • Related to Feature #77848: Make soft hyphens visible backend forms added
Actions #5

Updated by Riccardo De Contardi over 6 years ago

  • Category set to Backend User Interface
Actions #6

Updated by Susanne Moog 10 months ago

If you need this feature, you can use https://github.com/WapplerSystems/Shyguy/ as long as there is no core provided solution.

Actions #7

Updated by Ayke Halder 5 months 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?

See https://docs.typo3.org/m/typo3/guide-contributionworkflow/main/en-us/HandlingAPatch/Tips.html#decide-about-general-issues-before-fixing-nitpicks

  • 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

Actions

Also available in: Atom PDF