#110376CSP-friendly, file-aware alternative to the "Plain HTML" content element
Description
The use of “plain HTML” should be the exception. There may be times when you want to present a partner’s message on your own website, including their styling (fonts etc.), interaction options (JavaScript) and media (images, videos). This requires relaxing the CSP rules domain-wide with “unsafe-inline” for CSS and JS. Images have typically been stored in the fileadmin without deletion protection, which isn’t ideal either.
Using AI: I’ve created a code variant that circumvents this by allowing you to upload a CSS file, a JS file, and up to five images via FAL and integrate them through the backend. Links to the images can be inserted using a defined marker (using an older TYPO3 technique). (The image editor was omitted because it was assumed that the images are rendered web-ready.) “Plain HTML” is ultimately only a temporary solution for specific situations.
The included files of the zip-file require the “Content-Blocks” extension.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 1
History 1
-
Georg Ringer commented and changed status
NewRejected <span data-processor="relativetime" data-value="2026-08-05T07:21:57+00:00" > 08/05/26, 07:21 </span>
Thanks for creating this feature request.
Csp must be separated from the editing process as this element can be used by editors (which shouldn’t be done but anyway).
What you describe is the correct way to create content elements (native or content blocks) and implement what you really need.
Therefore closing the issue. Feel free to discuss via slack