#109670Camino Theme: lib.contentElement reset caused by fluid_styled_content dependency in Site Sets
Description
Hello,
The extension theme_camino implements a custom `lib.contentElement` TypoScript object from scratch, intentionally omitting a dependency on the core extension `fluid_styled_content` (FSC).
The Conflict
The Camino architecture relies on a dynamic `templateName` resolution based on the `CType` field:
lib.contentElement = FLUIDTEMPLATE
lib.contentElement {
templateName >
templateName.ifEmpty.cObject = TEXT
templateName.ifEmpty.cObject {
field = CType
required = 1
case = uppercamelcase
}
}
When a third-party extension (e.g., `mpc_vidply`) is installed that defines `typo3/fluid-styled-content` as a dependency in its `config.yaml`, the Site Set logic loads FSC after the Camino Site Set. Since FSC explicitly clears the object path via `lib.contentElement >`, the entire Camino rendering logic is purged.
Observed Impact
The system fails with an `InvalidTemplateResourceException`. This occurs because FSC replaces Camino’s dynamic `templateName` logic with a hardcoded `templateName = Default`.
Consequently, the Fluid engine searches for a `Default.html` template for every Camino-based content element within the FSC fallback paths. As these templates do not exist for Camino’s custom CTypes, the frontend rendering breaks instantly.
This behavior demonstrates a fundamental interoperability issue between custom theme engines and extensions enforcing a fluid_styled_content dependency via Site Sets.
Reviews 2
History 1016
-
Radostin Milenov commented <span data-processor="relativetime" data-value="2026-08-30T14:19:41+00:00" > 08/30/26, 14:19 </span>
-
Radostin Milenov commented <span data-processor="relativetime" data-value="2026-08-30T14:23:05+00:00" > 08/30/26, 14:23 </span>
That would however be more of a workaround. I believe bootstrap_package also has a similar problem with FSC.
-
Gerrit Code Review pushed patch set 1 for main to change 95477 status
NewUnder Review <span data-processor="relativetime" data-value="2026-08-30T16:16:39+00:00" > 08/30/26, 16:16 </span> -
Gerrit Code Review pushed patch set 2 for main to change 95477 <span data-processor="relativetime" data-value="2026-08-30T16:45:28+00:00" > 08/30/26, 16:45 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 95477 <span data-processor="relativetime" data-value="2026-08-30T17:05:08+00:00" > 08/30/26, 17:05 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 95477 <span data-processor="relativetime" data-value="2026-08-30T19:24:42+00:00" > 08/30/26, 19:24 </span>
-
Sebastian Klein commented <span data-processor="relativetime" data-value="2026-08-31T08:18:23+00:00" > 08/31/26, 08:18 </span>
Do we need a way to exclude certain site sets from inclusion? Something like
name: typo3/theme-camino
label: “Theme: Camino“
optionalDependencies:
– typo3/felogin
– typo3/indexed-search
– typo3/form
– typo3/seo-sitemap
conflicts:
– typo3/fluid-styled-contentoptionalDependencieswill load a set as soon as it is available in the TYPO3 installation, not if it is actually needed in this particular site. -
Gerrit Code Review pushed patch set 5 for main to change 95477 <span data-processor="relativetime" data-value="2026-08-31T08:24:03+00:00" > 08/31/26, 08:24 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 95477 <span data-processor="relativetime" data-value="2026-08-31T09:22:06+00:00" > 08/31/26, 09:22 </span>
-
Radostin Milenov commented <span data-processor="relativetime" data-value="2026-08-31T10:06:22+00:00" > 08/31/26, 10:06 </span>
Sebastian Klein wrote in #note-7:
> Do we need a way to exclude certain site sets from inclusion? Something like
>
> name: typo3/theme-camino
> label: “Theme: Camino“
> optionalDependencies:
> – typo3/felogin
> – typo3/indexed-search
> – typo3/form
> – typo3/seo-sitemap
> conflicts:
> – typo3/fluid-styled-content
>
>optionalDependencieswill load a set as soon as it is available in the TYPO3 installation, not if it is actually needed in this particular site.Isn’t that preventing you working with anything that depends on fluid_styled_content ?
-
Sebastian Klein commented <span data-processor="relativetime" data-value="2026-08-31T10:31:38+00:00" > 08/31/26, 10:31 </span>
> Isn’t that preventing you working with anything that depends on fluid_styled_content ?
The way I could imagine it to work would be:
- I add my site set dependencies as usual
- If a site setmy/featurehas its own dependency ontypo3/fluid-styled-content, TYPO3 could still load the configuration ofmy/featureand only excludetypo3/fluid-styled-contentOf course, there might be cases where the features of a site set will not work properly without all its dependencies. It may then still work if missing parts are added to the project’s sitepackage.
I would think if an integrator/developer decides to flag a particular site set as a conflict, there will be a good reason not to load its configuration.As you mentioned, the Bootstrap Package also uses
lib.contentElementand will have the same issues. It would complicate configuration if every package now has to ship their own variant oflib.contentElement. It is a TypoScript identifier that is extended by many third-party extensions. -
Radostin Milenov commented <span data-processor="relativetime" data-value="2026-08-31T11:17:45+00:00" > 08/31/26, 11:17 </span>
Yes exactly, hence the workaround proposed. If i understood correctly every new versio of typo3 will be shipped with a new custom theme, so it shouldn’t be critical. Look at the patch i would love feedback. Stefan Bürk already helped me identify a critical problem in it which is now fixed.
-
Sebastian Klein commented <span data-processor="relativetime" data-value="2026-08-31T12:11:44+00:00" > 08/31/26, 12:11 </span>
Your patch would fix the issue for the Camino theme, but at the cost of a breaking change in a minor TYPO3 version.
Also, it does not fix the current underlying shortcoming of site set dependency resolving.
As Stefan already pointed out,
lib.contentElementis needed for Extbase plugins. The identifier is hardcoded for the TypoScript cObjectEXTBASEPLUGIN. It is the foundation for content element rendering since TYPO3 7.6.Various third-party extensions extend
lib.contentElement. Some of these will add FSC as a dependency, even if it is not necessary. As the Bootstrap Package has the same template structure, many of these extensions will work fine with it.
IMHO, it would be a superfluous additional step to rename every theme implementation to something likelib.bootstrapPackageContentElement, and then referencelib.contentElementagain to reestablish plugin (and extension) compatibility.If it’s possible, I would prefer to fix the source of this issue instead of its symptoms.
-
Radostin Milenov commented <span data-processor="relativetime" data-value="2026-08-31T12:44:39+00:00" > 08/31/26, 12:44 </span>
Agree, but still the problem ist out there now. I don’t have a faster fix idea for it. You’re welcome to amend the patch if you do.
-
Andreas Kießling commented <span data-processor="relativetime" data-value="2026-11-14T11:38:31+00:00" > 11/14/26, 11:38 </span>
I wanted to demo the theme to a client only to find out i can’t showcase the fluid styled content elements…
IMHO this extension is not usable as a best-practice setup.If you build own content elements, you either should stick to the defaults and reuse the provided wrappers for content element layouts etc., or build everything on your own, but do not break the defaults. I can’t really think of a usecase for the theme extension in this state.
-
Georg Ringer commented <span data-processor="relativetime" data-value="2026-11-14T12:46:20+00:00" > 11/14/26, 12:46 </span>
@s-d-a this has been the first theme, and of course not everything has gone perfect. A theme should not depend on fluid_styled_content as this has a lot of other issues and might be removed in future. Talk to me if you want more information
That should not be that hard of a fix. Instead using lib.contentElement we could give it a theme specific name like lib.caminoContentElement for example. Atleast with the current way of site sets dependencies i don’t see e better solution. I’ll prepare the patch and we can discuss it further.