Review 14.3 Merged

95008[BUGFIX] Treat Messenger wildcard route as fallback

Stefan Bürk CR +2 V +2 Hard +667 −24 updated 07/30/26, 06:24

Commit message

Symfony Messenger transport routing configured in the
"routing" section of

  $GLOBALS['TYPO3_CONF_VARS']['SYS']['messenger']

always applied a wildcard route - a namespace wildcard
(My\Message\*) or the global '*' - in addition to any
matching specific route. A message that matched both a
specific route and a wildcard route was thus dispatched to
both transports. As TYPO3 ships a default catch-all route
'*' => 'default', every routed message was silently sent to
the default transport as well, and routing a message to its
specific transport only required unsetting the wildcard route
in an extension.

A wildcard route now acts as a fallback and is skipped as
soon as a more specific type - the message class, a parent
class, an implemented interface or a more specific namespace
wildcard - already matched. It only applies when no specific
route matched. This mirrors the upstream Symfony
SendersLocator resolution and makes the manual unset() of the
wildcard route obsolete.

Routing values may additionally be given as an ordered list
of transport identifiers to route a message to several
transports on purpose; the legacy single-string mapping keeps
working as the single-element array form.

Review

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

Issues 3

Files 7

Review log 34

  1. Stefan Bürk commented on patch set 1 07/30/26, 06:10

    Cherry Picked from branch main.
  2. core-ci voted on patch set 1 V +1 07/30/26, 06:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/105658

  3. Stefan Bürk voted on patch set 1 CR +2 V +2 07/30/26, 06:24

  4. Stefan Bürk merged patch set 2 07/30/26, 06:24