Issue Bug Rejected

#105482Mismatch between TypoScript and site configuration dependencies order

Benjamin Robinson 10/26/24, 11:08 updated 10/28/24, 08:19

Description

The order specified in the Site Configuration …

dependencies:
  - typo3/seo-sitemap
  - typo3/redirects
  - typo3/fluid-styled-content
  - typo3/form
  - typo3/indexed-search
  - r2/sitepackage

… is not or incorrectly taken into account in the loading order, see screenshot:

setup.gif

Since the TypoScript of the site package is loaded before indexed-search, the site package cannot override its TypoScript.
Settings like plugin.tx_indexedsearch.settings.displayAdvancedSearchLink = 0 in Sitepackage do not take effect.

A workaround would be to place the dependencies in the site package instead of in the Site Configuration. However, this is not ideal, as it means the dependencies can no longer be edited via the site module in the backend.

Reviews 0

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

Files 1

History 5

  1. Nikita Hovratov commented <span data-processor="relativetime" data-value="2024-10-26T20:00:25+00:00" > 10/26/24, 20:00 </span>

    This is probably not a bug. You should define your dependencies in the site package. At least this is the intended use case. Everything included at first-level should not depend on each other. What’s the point of the feature when used like the old static TS includes? I mean, the moment you override TypoScript from another extension you can simply add the dependency at the same time, or not?

  2. Benjamin Robinson commented <span data-processor="relativetime" data-value="2024-10-26T21:48:34+00:00" > 10/26/24, 21:48 </span>

    The sitepackage does not depend on the other extensions – it just overrides something if it has been loaded and works fine without it. I think that since you can create an order, it should be taken into account. I don’t see any system in the current ordering – it’s not even alphabetical.

  3. Markus Klein commented <span data-processor="relativetime" data-value="2024-10-27T19:01:51+00:00" > 10/27/24, 19:01 </span>

    Without a deeper look into the issue, a few thoughts from my side:

    Sitepackage is THE leading package in the system and should/must require all extensions used in the instance (your root composer.json only needs to require your sitepackage usually).
    The reason simply is that you want your sitepackage to “have the final word” when it comes to configuration and overrides.

    Having said that, it has been and still is the goal to make any configuration within TYPO3 independent of the extension’s loading order. While this is for sure no implemented everywhere yet, new API should not rely on extension loading order. So, there either has to be an explicit order defined by the user, or a dedicated ordering system (usually using the DependencyOrderingService).

  4. Benjamin Franzke commented and changed status New Rejected <span data-processor="relativetime" data-value="2024-10-28T08:16:38+00:00" > 10/28/24, 08:16 </span>

    The ordering of site set dependencies does not define ordering.
    They are ordered by dependencies, everything else is undefined.
    That means: If you require one set to be loaded after another, you need to express that in the (sub)set as a dependency.

  5. Benjamin Robinson commented <span data-processor="relativetime" data-value="2024-10-28T08:19:17+00:00" > 10/28/24, 08:19 </span>

    I understand and agree with you all. Thanks for the explanations.