Before I go ahead and implement my site's architecture, I'd like to check whether or not it's valid.
I have two taxonomy vocabularies that I want to use as part of my Pathauto settings. My site is a local accommodation guide, so I'd like to implement a URL structure like this:
^ ^ ^ | | |----- Accommodation name | |------------------- Location name |------------------------------------- Accommodation type
Which follows the syntax mywebsite.com/[accommodation type]/[location]/[accommodation name]
Up until now, I've found it impossible to do this using just taxonomy tokens. I always end up with paths that look wrong.
A way around this seems to be to set each accommodation type as its own content type (for example, 'cottage' content types, 'holiday apartment' content types etc), instead of just having one 'accommodation' content type as I currently have then set the path settings for each content type like so:
Cottage content types: cottages/[termpath-raw]/[titlepath-raw] Holiday apartment content types: holidayapartments/[termpath-raw]/[titlepath-raw]
Whilst this seems to produce the result I want, it feels more like a compromise than the correct solution. Before I go ahead and do this, I want to check that there isn't another way of setting up the path structure that I want using taxonomy tokens.
I'm also wondering what happens when I introduce multiple vocabularies for those content types - how will I ensure that the location vocabulary doesn't get replaced in the URL structure by another vocabulary (for example, if I use a vocabulary for holiday types - family, group, singles, couples etc - how do I ensure that this vocabulary doesn't take the place of the location vocabulary?).