Review main Merged Breaking

91000[!!!][FEATURE] Introduce submodule dependencies for backend modules

Oli Bartsch CR +2 V +2 Hard +380 −16 updated 10/17/25, 08:03

Commit message

Backend modules can now use the new
`dependsOnSubmodules` configuration
option to automatically hide themselves
from the module menu when they have no
accessible submodules.

This enables container modules to adapt
dynamically to user permissions and installed
extensions, keeping the module menu clean
and focused on actionable functionality.

The Web > Info module now uses this feature
to hide itself when all info submodules are
unavailable.

Review

  • Code review CR +2 Done
    • Oli Bartsch +2
    • Stefan Bürk +1
    • Benni Mack +1
  • Verified V +2 Done
    • Oli Bartsch +2
    • Stefan Bürk +1
    • Benni Mack +1
    • core-ci +1 CI

Issues 1

Files 10

Review log 1316

  1. Oli Bartsch uploaded patch set 1 10/10/25, 15:48

  2. core-ci voted on patch set 1 V +1 10/10/25, 15:59 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86418

  3. Josua Vogel commented on patch set 1 10/11/25, 15:06

    about.xlf:103

    ```suggestion <source>There are currently no functions available for this module.</source> ```

    about.xlf:106

    ```suggestion <source>There are currently no functions available for the %1s module.</source> ```
  4. Oli Bartsch commented on patch set 2 V +1 10/13/25, 05:56

    Published edit on patch set 1.
  5. core-ci voted on patch set 2 V +1 10/13/25, 06:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86512

  6. Josua Vogel commented on patch set 2 10/13/25, 07:10

    about.xlf:103 Reply

    Done

    about.xlf:106 Reply

    Done
  7. Benni Mack voted on patch set 2 CR +1 V +1 10/13/25, 15:29

  8. Stefan Bürk commented on patch set 2 10/13/25, 16:17

    The ModuleInterface itself is not internal .. should that not be considered public API then ? If yes, this would be a breaking change adding the new function to the interface and requires at least a breaking rest file along with the feature restfile stating the migration path for custom module implementations, adding the method to the module without a effect in v13 but satisfying the interface on an upgrade. Or am I wrong ?
  9. Oli Bartsch uploaded patch set 3 CR +1 V +1 10/13/25, 21:06

  10. Oli Bartsch commented on patch set 3 10/13/25, 21:08

    Reply

    I don't get the relation to v13 as this is main only, however I've added a breaking rst with a migration path.
  11. core-ci voted on patch set 3 V +1 10/13/25, 21:14 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/86580

  12. Stefan Bürk commented on patch set 3 CR +1 V +1 10/13/25, 21:42

    Reply

    Sure, this is breaking. But in case someone has a dual coreversion extension (v13 & v14) they could add the new method to the custom module .. in v13 without effect, in v14 satisfying the interface. Maybe it's just me having a couple of extensions in the company following dual core version supports (albeit no one having a custom module based on the interface). Thanks for adding the rest file.
  13. Benni Mack voted on patch set 3 CR +1 V +1 10/14/25, 08:39

  14. Oli Bartsch voted on patch set 3 CR +2 V +2 10/14/25, 08:40

  15. Oli Bartsch merged patch set 4 10/14/25, 08:40

  16. Lina Wolf commented on patch set 4 10/17/25, 08:03

    Unresolved