I think this module could really use pathauto/token support, so the subsite a node belongs to can be inserted in the seo friendly url.

Comments

bkildow’s picture

I agree with Marc. When first learning about this module, I was hoping that it would create paths for each subsite. However it does not seem to do this. Here is my use case for having such integration:

I have a content type called "page". I want to create two nodes from this content type, "nodeone" as part of the "exampleone" subsite and the other, "nodetwo", as part of the "exampletwo" subsite. When I visit each of these two nodes, I would like them to have separate paths related to the subsite for which they belong (for example: exampleone/nodeone and exampletwo/nodetwo).

I was able to get close to achieving this by using the menu replacement token in the pathauto's automated alias settings. So if I set up the pattern [menu]/[title-raw] it would accomplish the above if the node was in the subsite menu. What I would like see is a separate [subsite] token that could be used in pathauto's automated alias settings. This way if a node is assigned to a subsite but not in the menu, it will accomplish the above as well.

Thanks for your hard work on this module!

andrey.troeglazov’s picture

Issue summary: View changes
Status: Active » Fixed
andrey.troeglazov’s picture

Status: Fixed » Active