we're currently running into a problem with a new Umbraco-Project (Version 7.13.1) by trying to structure our content nodes.
We'd like to now if there is a "best practice" way to achive this.
What we're trying to achive:
We have a Content "Pages", which behaves like a folder and holds multiple "Page" document types - in this example content named "Home". (See image below) We'd like to have the "Home"-Content acting like an root-content and give it the URL "/" since it is the starting page.
Basically we want "Pages" to not have a URL at all, so "Home" would be the first content at root.
The problem we're running into:
The content "Pages" automatically gets the URL "/" from Umbraco which is the reason why the "Home" content can't be accessed under the root URL "/". We know a few workaround for this, but they all have massive disadvantages and don't seem to be nice solutions to us (Build-In redirect properties, custom URLProvider, IIS-Rewrite Rules).
Example:
Is there any other solution how to achive this?
If not, what is the best-practice one?
Thank you very much!
we tried as you said and it worked pretty well.
But we still have some questions:
To avoid problems and changing-necessity for hostnames on deployment, we'd like to know if it's possible to add a virtual path or something to the "Culture and Hostnames" like "~/"? We actually tried "~/" and "/" but it's not valid. Is there some kind of expression that we can add?
That way, we woudn't have problems between different environments and there is no necessity to add and change hostnames if they're changing.
Best Practice with folder structure in content section
Hi Community,
we're currently running into a problem with a new Umbraco-Project (Version 7.13.1) by trying to structure our content nodes. We'd like to now if there is a "best practice" way to achive this.
What we're trying to achive:
We have a Content "Pages", which behaves like a folder and holds multiple "Page" document types - in this example content named "Home". (See image below) We'd like to have the "Home"-Content acting like an root-content and give it the URL "/" since it is the starting page. Basically we want "Pages" to not have a URL at all, so "Home" would be the first content at root.
The problem we're running into:
The content "Pages" automatically gets the URL "/" from Umbraco which is the reason why the "Home" content can't be accessed under the root URL "/". We know a few workaround for this, but they all have massive disadvantages and don't seem to be nice solutions to us (Build-In redirect properties, custom URLProvider, IIS-Rewrite Rules).
Example:
Is there any other solution how to achive this? If not, what is the best-practice one?
Thanks, ModulAcht
Hi
Right click on Home, and Select "Culture and Hostnames" and add a hostname to the node.
That will make it the root node for your hostname.
Hello Michael,
Thank you very much! we tried as you said and it worked pretty well.
But we still have some questions: To avoid problems and changing-necessity for hostnames on deployment, we'd like to know if it's possible to add a virtual path or something to the "Culture and Hostnames" like "~/"? We actually tried "~/" and "/" but it's not valid. Is there some kind of expression that we can add?
That way, we woudn't have problems between different environments and there is no necessity to add and change hostnames if they're changing.
is working on a reply...