Project

General

Profile

Actions

Feature #105726

open

Resolve placeholders in Yaml config with site set settings

Added by Lars Peter Søndergaard about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2024-11-29
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Before, I could easily do:

routeEnhancers:
  NewsDetail:
    type: Extbase
    extension: News
    plugin: Pi1
    limitToPages:
      - '%settings.detailpids.news%'

as the settings were part of the config itself.

But now with site sets it's no longer possible, as the settings are stored in a separate file and are also not imported into the config.

I could of course add the settings to the config again or (which I'm currently doing) just specify the page ids directly instead of using placeholders.

It would be great if thise feature is extended to include site sets settings as well.

Greetings


Related issues 2 (2 open0 closed)

Related to TYPO3 Core - Feature #105819: Allow TYPO3 contextual configuration for site setsNew2024-12-13

Actions
Related to TYPO3 Core - Bug #105854: Imports are not resolved in settings.yamlUnder Review2024-12-20

Actions
Actions #1

Updated by Garvin Hicking about 2 months ago

Ref Slack: https://typo3.slack.com/archives/C025BQLFA/p1733211578969529

Question was asked whether ENV placeholder substitution could be used, or if not, why that is not a good idea :-)

Actions #2

Updated by Garvin Hicking about 1 month ago

  • Related to Feature #105819: Allow TYPO3 contextual configuration for site sets added
Actions #3

Updated by Lars Peter Søndergaard about 1 month ago

Hi! That discussion seems more about using placeholders (%env%) in site sets, where my issue is actually about using site set settings in the regular site (not site set) config (or did I misunderstand it?).

It works fine if the settings array exists directly in the site config, but ideally I would like to have the settings only in the site set settings and use placeholders in the site config to reference them, as my example above shows.

To summarize again: I want to use settings from the generated sites/mysite/settings.yaml in my sites/mysite/config.yaml

Greetings

Actions #4

Updated by Garvin Hicking about 1 month ago

Yes, all good. The two things only deal on a conceptual level with each other and I did not want to create a distinct issue for that. Question is how and if redundancy can be avoided IMO for both things, to allow defining "things" and re-using them.

Actions #5

Updated by Garvin Hicking about 1 month ago

  • Related to Bug #105854: Imports are not resolved in settings.yaml added
Actions

Also available in: Atom PDF