We have moved to GitHub Issues
Created by Robin Crama 06 Jun 2014, 09:31:50 Updated by Sebastiaan Janssen 06 Jun 2014, 10:24:03
Dit you ever create a node just to have the routing in place?
Example: You have /items that lists a lot of items You have a Theme page (christmas...) wich has only a couple of all the items. The Theme page has a button /christmas/items that shows these particular items.
Now the for the routing we have a items node under the christmas theme node. Useless for the content editor but needed for the routing.
So would it be great to add ghost children in the structure tab of a document type:
Allow at root .. Enable list view .. Allowed child nodetypes .. Ghost child nodestypes [nodeName, nodeType] + [nodeName, nodeType] + [nodeName, nodeType] +
These items represent nodes in the tree that doesn't need to show in the tree but need to be there always for the routing.
I'm not sure what you're trying to do but you should probably take advantage of custom routing - http://shazwazza.com/post/Custom-MVC-routes-within-the-Umbraco-pipeline or contentfinders - http://our.umbraco.org/documentation/Reference/Request-Pipeline/IContentFinder instead.
We're not going to overcomplicate the document type editor (which is already too complicated!) for edge cases like this.
Type: Feature (request)
Backwards Compatible: True
Due in version: