Jump to:
| Project: | Spaces |
| Version: | 7.x-3.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
We are trying to use purl and spaces to provided a kind of multisite setup. There are 2 taxonomy spaces set up.
One has the purl /cats and the other /dogs.
The end goal is to be able to have two nodes, one in each space:
node/1 accessible at the path /cats/about - which is part of the cats space.
node/2 accessible at the path /dogs/about - which is part of the docs space.
In order to be able to do this you would need to be able to assign both nodes to the url alias /about, since spaces and purl deal with automatically redirecting to (and prepending) /cats or /dogs. However, its impossible to create 2 url aliases that are the same. Right now, all I can do is have /cats/about and /dogs/about2. Obviously, thats no good.
If I give the nodes the aliases /cats/about and /dogs/about then after purl/spaces has prepended the purl prefix to the path, the path becomes /cats/cats/about and /dogs/dogs/about. Again, no good.
So, it seems that either I'm missing something, or we need the ability to tell purl/spaces to ignore parts of a url alias if they match the purl path - activating the space, but not prepending the purl to the path, since its already there as part of the alias.
Comments
#1
+1
this could also be an argument for using Spaces without PURL. if some property of a node or set of nodes (say, which group they belong to) determines a "space", then why not use that property to trigger behaviors? why is a PURL prefix required? you might wish all CAT group nodes to have the CAT prefix **whether or not** they have their own space. why a conceptual approach like spaces relies on the physicality of URL prefixes is not clear to me.