Allow different nodes per path alias

You can also do the reverse, I believe , though it can be hard to manage, since there are no reverse lookups. So you have to keep track of these nodes yourself.

In your scenario, do the following:

• Node 1
• Site 1 alias: foo
• Site 2 alias: bar
• Site 3 alias: bar

• Node 2
• Site 1 alias: bar
• Site 2 alias: foo
• Site 3 alias: bar

You'll want to experiment with how you set the default path for these nodes. Perhaps a better approach and explanation is:

• Node 1
• Path: bar (set using the Path field or PathAuto)
• Site 1 alias: foo (overrides Path)
• Site 2 alias: NULL (uses Path)
• Site 3 alias: NULL (uses Path)

• Node 2
• Path: baz (set using the Path field or PathAuto)
• Site 1 alias: NULL (uses Path)
• Site 2 alias: foo (overrides Path)
• Site 3 alias: NULL (uses Path)

The real trick here is what path to use in cases where you don't overwrite it. Now, if the node isn't visible on domains other than 1 and 2, it doesn't matter.

Yes, this statement is correct: In general, if the path isn't overriden, it should use what PathAuto sets

Is there support for something like domain pathauto? It would be very helpful to set these overridden URL's automatically instead of on an individual basis.

There is not. That would be a separate feature request.

I'd love to get this working, but trying to use the setup in #1 (beginning w/"Perhaps a better approach and explanation"), all I get is redirect loops. I'm using pathauo and have the dev version of Domain Path installed. How can I troubleshoot what's going on?

Looking at #1325088: Firefox: "Page isn't redirecting properly" (redirect loop), I wonder if my redirect loop issues have to do with Path Redirect (which I'm using in conjuction with pathauto). I'll try with Path Redirect disabled to see if that resolves anything.

In my case, disabling Path Redirect doesn't make any difference; I'm still getting unresolvable redirect loops if I try to have two different nodes (on two different Domain Access domains) with the same path.

I think upgrading globalredirect to 6.x-1.4 (from 6.x-1.2) may have solved my endless redirect loop issue.

On 6.x, updating to the most recent release of Global Redirect caused the redirect loops to go away.

See: http://drupal.org/node/1325088#comment-5644216