TYPO3 Core

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/40352

Suggested alternative solution:

Avoid use of RTE in system news. It's not nice but it would be the only clean solution to preserve BE/FE separation.

It may sound pretty categorical but the fact is that the HtmlViewHelper is just completely dependent on a heap of FE-specific objects and contexts. We might consider implementing an alternative, BE-specific ViewHelper but it will never be as comprehensive as the FE one - and it would also imply a custom RTE configuration and processing instruction object for that ViewHelper alone.

I recommend a "won't fix" here but I refrain from rejecting the issue.

In system news on login screen (during maintenance mode) links within RTE are still not rendered.

I am also pro TEXT-only system news input field.

Hmm, so rendering of links in backend-messages is still not possible in 7.6

<sarcasm>
Nice if you import these from a rss-resource.
</sarcasm>

+1 for fixing that in v7 LTS ...

Clemens Riccabona wrote:

Hmm, so rendering of links in backend-messages is still not possible in 7.6
[...]
nobody can get to the original news-entry ...

+1 for fixing that in v7 LTS ...

To clarify: i am totally fine with plaintext system news.
But the link-feature is a really most common part of any type of "news" all over the world!
And additionally don't hint the editor of such a news the wrong way by providing him/her with a full-featured RTE!
This is awful, to say it the nice way.

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48580

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48580

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48580

Came across this issue when having similar problems with the restler extension. What helped in my case (beside "simulating" FE) was correctly registering the content objects in

$GLOBALS['TYPO3_CONF_VARS']['FE']['ContentObjects']

Not sure if this is enough - at least links are now correctly generated - in my case - using cObj->parseFunc().

Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/48580

Still present in TYPO3 version 9.5.11, "auto-linking" workaround still works.

Still present in 10.4 and the workaround does not seem to work, everything just gets stripped away.

I would be fine with changing format.html to just format.raw, we could disable the page links etc. for the RTE and just keep external url and maybe email. The basic formatting stuff like bold, lists etc. should work

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/70740

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/70740

Reverted, see

→ https://review.typo3.org/c/Packages/TYPO3.CMS/+/70977
→ https://review.typo3.org/c/Packages/TYPO3.CMS/+/71020