#99316Move all Fluid Styled Content specific components to EXT:fluid_styled_content
Description
Current state
The default CTypes and their rendering definition are shipped by Fluid Styled Content. But templating and configurations are spread across three system extensions:
- EXT:fluid_styled_content:
- TypoScript base rendering definition (lib.contentElement)
- TypoScript rendering definition (per CType)
- CType templates, layouts and partials
- EXT:frontend:
- Necessary tt_content fields (SQL)
- CType definitions in TCA
- TypoScript (tt_content = CASE)
- EXT:backend:
- Backend preview
As described in the big vision #98134, all components related to Fluid Styled Content, should be moved to EXT:fluid_styled_content, so that it can be deprecated and moved to FriendsOfTYPO3 as an independent package later on.
Reviews 2
History 69
-
Benni Mack changed parent task #98134 <span data-processor="relativetime" data-value="2022-12-08T16:34:31+00:00" > 12/08/22, 16:34 </span>
-
Lidia Demin changed status
NewIn Progress assigned to Lidia Demin <span data-processor="relativetime" data-value="2022-12-08T16:36:20+00:00" > 12/08/22, 16:36 </span> -
Gerrit Code Review pushed patch set 1 for main to change 76996 status
In ProgressUnder Review <span data-processor="relativetime" data-value="2022-12-08T16:57:22+00:00" > 12/08/22, 16:57 </span> -
Lidia Demin changed category status
Under ReviewIn Progress <span data-processor="relativetime" data-value="2022-12-12T20:00:41+00:00" > 12/12/22, 20:00 </span> -
Gerrit Code Review pushed patch set 2 for main to change 76996 status
In ProgressUnder Review <span data-processor="relativetime" data-value="2023-01-20T14:40:14+00:00" > 01/20/23, 14:40 </span> -
Lidia Demin changed removed the assignee <span data-processor="relativetime" data-value="2023-10-31T07:42:53+00:00" > 10/31/23, 07:42 </span>
-
David Bruchmann commented <span data-processor="relativetime" data-value="2024-04-27T18:08:47+00:00" > 04/27/24, 18:08 </span>
-
Benni Mack commented and changed status
Under ReviewRejected <span data-processor="relativetime" data-value="2024-09-05T21:11:44+00:00" > 09/05/24, 21:11 </span>Closing this issue:
- We need to distinguish between the fields that all Content Types need (“bodytext” is quite common) and the actual CTypes.
- EXT:contentblocks is working on adding atomic versions, so just “moving” everything to FSC isn’t the solution – at least right now. -
Gerrit Code Review pushed patch set 4 for main to change 92249 status
RejectedUnder Review <span data-processor="relativetime" data-value="2026-05-21T19:53:23+00:00" > 05/21/26, 19:53 </span>
As it could be seen with the switch from CSC to FSC it’s was quite useful that CTypes never have been bound to CSC but rather been independently.
I don’t think that merging everything in FSC would be a good idea.
The controversial assumption that some some things belong to FSC can therefore be verified on the base if another rendering library could handle an element, or if the element is really so specific bound to FSC that it’s reasonable to move it in the FSC extension. Having seen the Patch it seems that rather all CEs shall be moved to FSC, which—like explained—would remove all useful definitions when the rendering extension is changed. This would add an huge overhead task to implement different rendering, without offering benefits by moving definitions in FSC.