TYPO3 Core

I encountered this as well.

In my case I had additionally "limitToPages" set for both enhancers, with the same page ids.

And after digging a bit (a lot actually), I realized what the issue is:

When "limitToPages", "extension" and "plugin" are all the same over multiple Extbase enhancers, then the list of routes "overrides" each other. The effect is similar to an array_merge of the routes.

So in the example above the '/list/{page}' route overrides the '/news/{news_title}' route, because they're on the same position (index 0) of the routes list.

Every route gets added to the RouteCollection for the current page (created in \TYPO3\CMS\Core\Routing\PageRouter::matchRequest) and in the case of the ExtbasePluginEnhancer, each route gets a key using the extension and plugin name as namespace, and an index $i, this $i value however, restarts for every new Extbase enhancer, causing enhancers with the same namespace to override each other:

\TYPO3\CMS\Core\Routing\PageRouter::matchRequest

            $pageCollection = new RouteCollection();
            [... omitted ...]
            $enhancers = $this->getEnhancersForPage($pageIdForDefaultLanguage, $language);
            foreach ($enhancers as $enhancer) {
                if ($enhancer instanceof RoutingEnhancerInterface) {
                    $enhancer->enhanceForMatching($pageCollection);
                }
            }

\TYPO3\CMS\Extbase\Routing\ExtbasePluginEnhancer::enhanceForMatching

    /**
     * {@inheritdoc}
     */
    public function enhanceForMatching(RouteCollection $collection): void
    {
        $i = 0;
        /** @var Route $defaultPageRoute */
        $defaultPageRoute = $collection->get('default');
        foreach ($this->routesOfPlugin as $configuration) {
            $route = $this->getVariant($defaultPageRoute, $configuration);
            $collection->add($this->namespace . '_' . $i++, $route);
        }
    }

I stumbled upon this issue, because I had a case where I split the extbase enhancer over three enhancer entries, all with the same limitToPages/extension/plugin values. And because they had multiple routes, some of them worked perfectly fine, and others did not, which caused a lot of confusion on my end.

Anyway: An easy solution (for now), is to simply merge the different routing enhancers into one.