Skip to main content

[BUGFIX] Restore backend module rerouting functionality

Due to the changes in #99620, it is now possible
for a second level module to not define any route.
Such module then automatically uses the routes
from the first available sub module (third-level).

However, this now led to the fact that it was no
longer possible for the BackendModuleValidator
to restore the actually last used third-level module
of such sub modules, because the module object
in the Route object got replaced by the fallback.

This use case is now also properly handled by
checking whether the resolved module is the
request modules' fallback.

Resolves: #99684
Related: #99620
Releases: main
Change-Id: I8cd19417fa66593dd4c612a07723dcbcf5162f5f
Reviewed-by: Stefan Bürk <>
Tested-by: core-ci <>
Tested-by: Christian Kuhn <>
Reviewed-by: Christian Kuhn <>
Tested-by: Stefan Bürk <>

[BUGFIX] Avoid usage of dummy controller for web_ts module

The TypoScript module (web_ts) is not directly
accessible and always redirects to the first
available third level module. This patch resolves
the necessity to define a default route for the
module, which previously referenced a dummy

Resolves: #99620
Releases: main
Change-Id: I6912ce65cec26f36745aa1aa9355db78e655b013
Tested-by: Benni Mack <>
Tested-by: core-ci <>
Reviewed-by: Anja Leichsenring <>
Tested-by: Anja Leichsenring <>
Reviewed-by: Benni Mack <>
Tested-by: Christian Kuhn <>
Reviewed-by: Oliver Bartsch <>
Reviewed-by: Christian Kuhn <>
Tested-by: Oliver Bartsch <>