Press Ctrl / CMD + C to copy this to your clipboard.
Copied to clipboard
Flag this post as spam?
This post will be reported to the moderators as potential spam to be looked at
Topic author was deleted
Oct 08, 2012 @ 17:37
URL not as expected on second level nodes
Problem:
Given a content tree as follows, the URLs in parenthesis don't make sense IMO:
Content
-Document 1 (/) Correct
--Document 2 (/document-2.aspx) Correct
---Document 3 (/document-2/document-3.aspx) Correct
-Document 4 (/document-4.aspx) Correct
--Document 5 (/document-5.aspx) ??? Should be /document-4/document-5.aspx ?
---Document 6 (/document-5/document-6.aspx) ??? Should be /document-4/document-5/document-6.aspx ?
Why doesn't Document 5/6 include Document 4 in the url as they do in document 3 and document 6?
We are seeing this on 4.7.2 and 4.9. This may be intended behavior, but it seems that Document 4 and 5 should have a parent/child url at least.
We are building a multiple area site and would prefer that we don't have to use strongly named content pages, we just want them to have to be unique to their hierachy.
The point is, the situation you describe is an anomaly and is not really supported. There should not be two root nodes (document1 and 4) without specified hostnames, when HideTopLevelNodeFromPath is enabled. Because HideTopLevelNodeFromPath is true, the url of _any_ root document should be /. Because that would create a duplicate, the url of document 4 reverts to /document-4 but really, that's just because we don't know what to do.
Then for document 5, 6, we go back to the normal url scheme.
You should either disable HideTopLevelNodeFromPath, or group the whole site under one document eg move document 4 under document 1, or assign hostnames to document 1 and document 4.
Perfect, thank you Stephen. I changed the HideTopLevelNodeFromPath to false. We are doing a multi-site/one-Umbraco core setup and that will work nicely.
For any follow-on readers:
web.confg --> <add key="umbracoHideTopLevelNodeFromPath" value="false" /> <---change from true to false
As you've found, Umbraco is flexible enough to handle any situation you might want. But you'll want to consider the umbracoHideTopLevelNodeFromPath and useDomainPrefixes settings if you have multiple sites in one installation or deviate from the default best-practice of having all content for a site beneath its home page.
So no bug here per se except that you didn't realize the default content structure that is assumed by the default settings and where to change those settings.
But as I say, there's lots of flexibility to architect your content tree they way you want.
Topic author was deleted
URL not as expected on second level nodes
Problem:
Given a content tree as follows, the URLs in parenthesis don't make sense IMO:
Why doesn't Document 5/6 include Document 4 in the url as they do in document 3 and document 6?
We are seeing this on 4.7.2 and 4.9. This may be intended behavior, but it seems that Document 4 and 5 should have a parent/child url at least.
We are building a multiple area site and would prefer that we don't have to use strongly named content pages, we just want them to have to be unique to their hierachy.
Hope that made sense.
The point is, the situation you describe is an anomaly and is not really supported. There should not be two root nodes (document1 and 4) without specified hostnames, when HideTopLevelNodeFromPath is enabled. Because HideTopLevelNodeFromPath is true, the url of _any_ root document should be /. Because that would create a duplicate, the url of document 4 reverts to /document-4 but really, that's just because we don't know what to do.
Then for document 5, 6, we go back to the normal url scheme.
You should either disable HideTopLevelNodeFromPath, or group the whole site under one document eg move document 4 under document 1, or assign hostnames to document 1 and document 4.
That being said, I agree it's a bit surprising...
Comment author was deleted
Perfect, thank you Stephen. I changed the HideTopLevelNodeFromPath to false. We are doing a multi-site/one-Umbraco core setup and that will work nicely.
For any follow-on readers:
web.confg --> <add key="umbracoHideTopLevelNodeFromPath" value="false" /> <---change from true to false
Final results when changing that setting:
As you've found, Umbraco is flexible enough to handle any situation you might want. But you'll want to consider the umbracoHideTopLevelNodeFromPath and useDomainPrefixes settings if you have multiple sites in one installation or deviate from the default best-practice of having all content for a site beneath its home page.
So no bug here per se except that you didn't realize the default content structure that is assumed by the default settings and where to change those settings.
But as I say, there's lots of flexibility to architect your content tree they way you want.
cheers,
doug.
Comment author was deleted
@Doug, thanks.
is working on a reply...