Domain no longer respects Domain Source and redirects to chosen source url

Are you using any third-party domain module?

Can you list all the domain-related modules that are enabled on your site?

Could you give us a reproducible scenario from a fresh Drupal instance?

Some domain-related custom code may be?

Domain Unique Path Alias is also a third party module.

Just started a fresh Drupal 10.5.3 instance with Domain 2.0.0-beta3.

I’m not seeing the redirect behavior you’re describing.

As far as I know, that isn’t a standard feature of the Domain Source module.

Could you try to reproduce your problem on a fresh Drupal 10 instance please?

Otherwise, I won’t be able to help you much.

I'm having this issue as well. I will try to post some reproducible steps.

It would be really helpful to have a reproducible scenario on a fresh Drupal installation that works with beta3 but fails with beta4.

I experienced a similar issue. Menu links pointing to external domains were not re-written anymore after the upgrade from Drupal 10.4.6 to 11.2.5 and Domain 2.0.0beta2 to beta4 and 5. Links set via the link field in nodes were still correctly re-written to link to external domains.

I was not able to restore functionality through downgrading to beta2 and found out that in the DomainSourcePathProcessor.php of domain_source the function DomainSourceRouteMatcher::routeMatch($path) did not return a valid route info.

Instead of digging further I tried to apply the core patch from https://www.drupal.org/project/drupal/issues/3202329#comment-16226547 which makes the path processor bypass the DomainSourceRouteMatcher::routeMatch function and that solved the issue for me.

Hi @nebel54, could you give us a bit more details about this:

I (...) found out that in the DomainSourcePathProcessor.php of domain_source the function DomainSourceRouteMatcher::routeMatch($path) did not return a valid route info.

Sorry, I am not able to investigate the issue further at the moment (I might have time in the evening). But the method returned NULL instead of the route info.

I got too curious and did a few more tests:

Steps to recreate:

Drupal: 11.2.5
Domain: 2.0.0-beta5

Only domain and domain_source modules are activated, minimum setup with two subdomains

- Create a node on domain2 without path alias
- Add the node to a menu (/node/2)
- Menu link has correct domain2 link
- Add a path alias (/my-path) to the node
- Url in Menu still shows correct link, as the menu has still the plain node url stored (/node/2)
- Edit menu again use /my-path as link
- Expected: Link should point to domain2, instead points to /my-path on default domain, when opening /my-path the node is also not redirected to domain2

In DomainSourceRouteMatcher::doMatchCollection() the matcher tries to match /my-path to the regex "{^/node/(?P|d+)$}sDuu", which then returns NULL.

@nebel54 could you give a try to change the outbound path processor priority like this (90 -> 400) :

  domain_source.path_processor:
    class: Drupal\domain_source\HttpKernel\DomainSourcePathProcessor
    arguments:
      [
        '@domain.negotiator',
        '@module_handler',
        '@entity_type.manager',
        '@config.factory',
        '@path.matcher',
      ]
    tags:
      - { name: path_processor_outbound, priority: 400 }

Seems to fix the problem on my side.

Will create an MR to see if it generates any side effects.

Ok, looks like we might break this: #2973694: Outbound path processor does not have access to language and then redirects.

Let’s try a different approach.

Good catch! Yes - it would fix this issue though :) I checked on the small test setup & the site that I originally encountered this issue on.

The MR also fixes this issue for me.

@nebel54 @cindytwilliams

I worked on another fix (MR 242) that preserves compatibility with translated contents.

Could you give it a try and give me an RTBC if it works for you? Thanks.

I have added a series of path alias functional tests so we don't get hit again by this problem in the future.

The latest MR changes are working for me.

Works for me as well! That is an impressive amount of tests you have added @mably! Thank you!

Let's still hope that #3202329: Outbound path processors miss the route name and parameters lands in core soon!

Let's still hope that #3202329: Outbound path processors miss the route name and parameters lands in core soon!

That would definitely bring a significant performance improvement when using the domain source path processor.

Let's merge this for now.

Hi,
I´m on drupal 10.5.3 and domain 2.0.dev.
I have a menu where 3 domains each have a block with their links (= each domain has its front page on menu level 0 and the corresponding subpages are linked below it, in level 1).
Each node is assigned to one of the three domains via the_domain_source field.
The links in the menu are created normally (using the node ID rather than as an absolute link) and have always correctly led/redirected to the respective domain.

After updating today (including the database update) to the new .dev version from October 7, 2025, the redirects no longer work.
I had to revert to the "old" .dev version.

Hi @4kant, it looks like we have found another edge case that is not covered by our functional tests.

I added in latest dev a new functional test to ensure that menu links referencing content with a defined domain source field are handled correctly.

Can you give a full reproducible scenario on a fresh Drupal 11 install please?

BTW what do you call the "old" dev version?

Hi @mably,
thanks for your quick reply.
The "old" dev version: I can´t find a version number in any of the .info-files. It always says: " version: VERSION".
But the date of the info files is April 28th.

Don´t know if or when i can give you a full reproducible scenario on a fresh Drupal 11 install. I do my best.

Thanks!

If no reproducible scenario is provided, I’ll close this issue in 3 months.

I've now installed a clean Drupal 11 installation with domain 2.0.0-beta6 and configured it according to my existing Drupal instance.
Everything worked correctly in Drupal 11. All menu items linked to the correct domain.

I then repeated the process with my Drupal instance (10.5.3).
Unfortunately, the menu links aren't interpreted correctly there – as described above.

I will do another install with a clean drupal 10 installation and get back here soon.

Postponing until we get new elements allowing to work on it.

Menu links are displaying fine on my 10.5.3 instance. So I cannot reproduce the problem for now.

Whatever has happened in the meantime:
The current dev version no longer has this bug. Everything is running perfectly.
Thanks!

@4kant Thanks for confirming that the issue has been resolved.

@mably can this change released in domain version 2.0.0 as well?

@cindytwilliams it's already been merged on the 2.0.x dev branch.

I plan to make a new beta release at the end of the month.

Ah, thank you!