whenn you create an url alias that points to an existing node url, it will create a node-url-alias. Those are unfortunately not shown in the list of url-aliases (hence it looks like they disappear), but you can see them if you click on the icon corresponding to the given node in the navigation treemenu and on the pop-up menu choose advance | url-alias management.
There is already a feature request in the tracker to add a management page where all of those aliases are listed, as having to check node by node is a bit of a waste ot time / unfeasible.
As for redirecting "/news" to "/home/news", I think the best solution is to rename or delete the "/news" object (and then add an url alias). What use is an object that cannot be accessed because it redirects to another node object?
Principal Consultant International Business
Member of the Community Project Board
In my case i use the url translator system to "hide" a parent folder full view that shouldn't be seen.
For exemple i have this tree "Home -> Skateboard -> News".
I don't want users to be able to hit "/skateboard" because its only a folder thats hold subfolders. Instead i want the system to display "/skateboard/news".
Is the new url translator able to deal with this ?
Because in 3.9 or 4.0 the url translator kind of override the node publication url_alias.
If i understand the process, a certain object say "content/view/full/2" can't have multiple url_aliases if those url_aliases already exists ?
To hide a node completely while keeping children visible, you can move it to a section that users have not access to, and you're done (if the node already has children, you will need to move them back to standard section).
There is a nice tutorial in articles section: "Helper Child Nodes: User-Friendly Search Results and Preventing Full Node Views" that might also give you some ideas
Principal Consultant International Business
Member of the Community Project Board
You must be logged in to post messages in this topic!
