Use Site Set variables in backend CSS?

[the-andyman]

Is it possible, to use variables like {$page.setting.variablename} from site set settings.definitions.yaml in the backend.css and/or frontend.css?
The inline solution from the old issue didn't work for me.

[nhovratov]

Did you load Site Settings into your template?

[the-andyman]

Thanks for the quick reply.
The Site Settings are loaded in my own "Sitepackage".
I have no problems to access the values via typoscript or in fluid templates.
But i can't access the variables in the content blocks templates.
Do i have to include something additional in these templates?

Here is an example (part) of an backend previews template:

<f:section name="Content">
<f:asset.css identifier="content-block-css/card" href="{cb:assetPath()}/card-preview.css"/>
<f:asset.css identifier="content-block-css/card">
div.card.bg-primary {
  background-color:{$page.styling.colorbgprimary} !important;
  color: {$page.styling.colorprimary} !important;
}
</f:asset.css>
</f:section>

[jonaseberle]

Site settings are available in Fluid Templates when you explicitly add them.

You'll need something like (Typoscript settings)

lib.contentBlock {
  dataProcessing {
    # https://docs.typo3.org/m/typo3/reference-typoscript/12.4/en-us/DataProcessing/SiteProcessor.html
    110 = site
    110.as = site
  }
}

Then your example should work, although I would by wary with your full example with potential Fluid parsing problems due to { in CSS. (There is a Workaround: assign { to a variable and use it instead of {...)

[the-andyman]

I tried the following code:

lib.contentBlock = FLUIDTEMPLATE
lib.contentBlock {
	variables {
		colorprimary = TEXT
		colorprimary.value = {$page.styling.colorprimary}
		colorbgprimary = TEXT
		colorbgprimary.value = {$page.styling.colorbgprimary}
	}
	dataProcessing {
		10 = content-blocks
		110 = site
		110.as = site
	}
}

In the frontend the variables are now successfully set.
But in the backend-preview no variables are set.
Am i missing something?

[nhovratov]

You don't have a site variable in BE previews. I can see, if it's possible to add one.