Issue Bug Rejected

#105517TYPO3 13.4: Using site sets the content of some extensions ext_typoscript_setup.typoscript is not loaded

Lina Wolf 10/30/24, 06:35 updated 10/31/24, 10:54

Description

In my installation, which is using site sets, the file ext_typoscript_setup.typoscript of some Extensions gets loaded and of some other extensions it gets ignored

So I am wondering if maybe for some reason the site set is unsetting the TypoScript from ext_typoscript_setup.typoscript in some cases but not others, maybe regarding loading order

For example causing this problem: https://github.com/krausandre/wsm-form-spamshield/issues/14

It seems like the loading order is affecting weither or not the `ext_typoscript_setup.typoscript` of a certain extension is loaded or not.

After doing an composer req or composer remove the `ext_typoscript_setup.typoscript` of an extension which was loaded before suddenly disappears or vice-versa.

Reviews 2

History 2

  1. Benjamin Franzke commented and changed status New Rejected <span data-processor="relativetime" data-value="2024-10-30T07:34:28+00:00" > 10/30/24, 07:34 </span>

    Hey Lina,

    thanks for you report!

    Site sets do not load any ext_typoscript_setup.typoscript files, by design, as we strive for zero global TypoScript.
    (Are you sure it is loaded for some? I guess they probably include that typoscript via other API as well then…)
    See following change for the motivation: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83722

    If someone really really needs global typoscript in sets, than that’s doable via ExtensionManagementUtility::addTypoScriptSetup(), see for an example were we had to revert to that because of EXT:form as well:
    https://review.typo3.org/c/Packages/TYPO3.CMS/+/86413/7/typo3/sysext/form/ext_localconf.php

    Although again: It is not suggested to add global TypoScript:
    Whenever possible, please provide the TypoScript as a set to make it dependable by other sets.

    In case someone needs global TypoScript for legacy sys_template users only, then
    @ExtensionManagementUtility::addTypoScriptSetup(content: …, includeInSiteSets: false)@ is the better option.
    That allows to provide global TypoScript for sys_template records, but allows to make the TypoScript available as set for set users.

  2. Lina Wolf commented <span data-processor="relativetime" data-value="2024-10-31T10:54:09+00:00" > 10/31/24, 10:54 </span>

    `ext_typoscript_setup.typoscript` is widely used by extensions extending the form backend module, i.e. by loading

    `
    module.tx_form {
    settings.yamlConfigurations {
    1678469420 = EXT:wsm_form_spamshield/Configuration/Yaml/BaseSetup.yaml
    }
    view {
    partialRootPaths {
    1678469420 = EXT:wsm_form_spamshield/Resources/Private/Frontend/Partials/Forms/
    }
    }
    }
    `
    Was there a breaking change stating that `ext_typoscript_setup.typoscript` if so I missed that one. We definately have to update the docs as currently they state that `ext_typoscript_setup.typoscript` is loaded globally not buts and ifs.

    Also I think there is a way needed to configure form without having to use TypoScript but that is another matter.