Can this module be used to resolve the same path to different nodes on different domains?

Created on 24 May 2023, about 1 year ago
Updated 25 May 2023, about 1 year ago

In my use-case, I have two domains... say... alpha.com and beta.com. There are two nodes (say, 1 and 2), each assigned to their domain:

alpha.com/node/1
beta.com/node/2

Both of these are the About Us pages for the domain and need to have about-us as the alias.

Using core Path module will only let me assign "about-us" to one of the nodes. The 2nd gets duplicate path complaints. Some content has been migrated across which bypassed this validation; in this case, Drupal is only picking the "first" alias and the 2nd site ends up rendering the content for the first site.

I thought this module would let me work around this. However it doesn't seem to help.

When enabled on those two nodes I can see entries for it in the domain_path table, each one assigned to the appropriate domain.

When I request alpha.com/about-us, everything works great (I get the right content for the right site)... When I request beta.com/about-us, I get You are not authorized to access this page.... When I inspect the markup on the page there are indications that the node ID is 1 and not 2 (as expected)... It looks like Drupal is still resolving using Path?

πŸ’¬ Support request
Status

Closed: duplicate

Version

1.2

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom nicholasThompson

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024