Bug #27743: CMS/BE: text-version of a richtext-field contains tag-fragments - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #27743

closed

CMS/BE: text-version of a richtext-field contains tag-fragments

Added by Stefan Neufeind over 13 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

Backend User Interface

Target version:

Start date:

2011-06-28

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

4.6

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

As can be seen in the attached screenshot the text-version (displayed the page-view in BE) contains "fragments" that (imho) don't really belong there.
What is shown is the "first attribute of empty tags". And there is a specialised strip_tags()-version that, according to the phpdoc, was created just for this purpose and that is used only in renderText() for the BE.

The output from for example the page-module of TemplaVoila is as you would expect it - no such "fragments". It leads to irritated backend-users.
The only real "use-cases" for this might be tags like <LINK abc@example.com> where the email-address would be fetched from. However since using richtext becomes more common these days as it was maybe a few years ago I think we should remove this.

PS: Since the same behaviour also exists in 4.5 we maybe should backport it there as well if accepted.

Files

strip_tags_first_attribute.png (13.2 KB) strip_tags_first_attribute.png

Screenshot of first attributes shown.

Stefan Neufeind, 2011-06-28 16:42