Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I have three nodes, which are domain-specific variations on the same content. Each of which has a different path within the three domain's sites out of necessity-- preferably they would all have same path with the only difference being the subdomain. Vanilla Drupal can't do this, but this module can.
Only problem is I can't seem to assign a domain-specific path to a menu link, which takes all the fun out of things. See attachment.
And to the developers: Thanks for this module, it's truly pure awesome.
| Comment | File | Size | Author |
|---|---|---|---|
| Screen shot 2011-04-19 at 11.48.48 AM copy.png | 77.14 KB | DanielF |
Comments
Comment #1
agentrickardI think if you just enter the 'base' url in the menu (like the node/NID) then the aliasing will be handled for you.
Otherwise, this would be a feature request to change how menu link validation is handled, not a bug.
Comment #2
DanielF CreditAttribution: DanielF commentedI tried that, and it did catch it, but it only converted it to the standard path alias I supplied using Drupal's core functionality, not the domain-specific path.
I think this should be critical-- if you can't use a domain-specific path in a menu, users will see node/#, or the path you specified using Drupal core's path module. I'll leave it to you, agentrickard, whether that should be the case. Thanks again for this module!
Comment #3
agentrickardI wonder if this is a menu cache issue.
Comment #4
agentrickardComment #5
agentrickardUsing node/# (by assigning a node to the menu using the node form) works fine for me.
Note that the node must be assigned to 'all affiliates' and not have a source domain set for the url to change on each domain.
Looking at the screen shot again, you can't enter a Domain Path url into the menu form. It won't validate. You must use the base node/# piece.