Issue Bug Closed

#109259404 instead of real page shown with slug being identical to site base

Franz Kugelmann 03/16/26, 14:19 updated 08/11/26, 08:46

Description

This is probably a rare edge case, but happened with one of our customers.
Happens in v12, v13, v14.

Multi-Site-Setup with following base:
first site – base: /
second site – base: /t3/

Now if the first subpage of the second site has the title t3 this results correctly to slug
/t3/t3/

The frontend however returns 404, because the Route is not correctly matched.
Luckily, the fix is easy, see attached patch.

Reviews 3

Files 1

History 814

  1. Franz Kugelmann changed attached matchCorrectRouteToFindCorrectSite.diff <span data-processor="relativetime" data-value="2026-03-16T14:24:37+00:00" > 03/16/26, 14:24 </span>

  2. Garvin Hicking commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-03-16T19:53:52+00:00" > 03/16/26, 19:53 </span>

    Could you put this in our patch tracker maybe so that CI tests can be run and you will be properly attributed? Thanks a lot!

  3. Franz Kugelmann commented <span data-processor="relativetime" data-value="2026-03-18T16:39:17+00:00" > 03/18/26, 16:39 </span>

    Yepp! Thanks for the nudge to not being so lazy. Coming soon, need to setup the process.

  4. Gerrit Code Review pushed patch set 1 for main to change 93273 status Needs Feedback Under Review <span data-processor="relativetime" data-value="2026-03-19T09:53:45+00:00" > 03/19/26, 09:53 </span>

  5. Franz Kugelmann commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-05-07T10:05:10+00:00" > 05/07/26, 10:05 </span>

    Applied in changeset commit:c6b1ca1b9ae09682b2f922510c55da2e318c3504.