Issue Feature Rejected

#99179Add stdWrap capabilities to RecordsXmlSitemapDataProvider settings

Andreas Kießling 11/24/22, 11:02 updated 07/28/24, 07:04

Description

This was already reported in #86914 but rejected.
I do not agree with that decision, maybe i can convince you to to change your mind.

In my setups, i strive for having configuration settings centralized. I extend the site configuration and site language depending on the project requirements.
Thus the page IDs for e.g. record storages and detail views go in there, so i can use them everywhere.

For “simple” setups, a lot of settings can go into settings block of a site config and are thus available as TypoScript constants. But when they need to be language specific, i can not access them this way and would like to use stdWrap data functions. Hence it would really help if settings accept stdWrap.

Example: while the website is build as single tree, some records are not translatable and created independently in different storage dirs. I would like to save this in the siteLanguage and access it via https://docs.typo3.org/m/typo3/reference-typoscript/main/en-us/Functions/Data.html?highlight=sitelanguage#sitelanguage

https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Seo/XmlSitemap.html#xmlsitemapdataproviders

pid = TEXT
pid.data = siteLanguage:record_storage_pid

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 2

  1. Benni Mack changed Related to #86914 06/06/24, 11:32

  2. Georg Ringer commented and changed status New Rejected 07/28/24, 07:04

    Hey Andreas,

    I am rejecting this issue once again as we try to remove stdwrap usages. Nothing happened in last year in this regard and also nothing will probably happen in future.

    hope you understand. if you don’t agree, feel free to contact me via slack!