I think it could happen if you've updated the value of that key after the pages have been published, so the links won't get updated until you've republished the entire site (which would also be the solution in your case). Right click any top level node (childs of 'Content') and perform a publish and additionally, right click 'Content' node and choose Republish entire site.
Just wanted to come back to say that this problem reared its ugly head again recently... And your fix fixed it. Cheers!
I think it didn't work the first time round because there were (somehow) nodes with the same name with the same parent. Not sure how that happened. That was killing the 'republish'.
Creating new page -> error
Weird thing started happening. Wondering if anyone had any pointers....? (recent Umbraco patch has been applied, as has recent Microsoft patch)...
In some sections of the site I can create new pages without error. In other sections it's trying to create them as
/my-home-page-name/some-folder/my-page.aspx
rather than
/some-folder/my-page.aspx
Any ideas? It wasn't doing this last week.
Thanks,
If it helps, my site structure is
content
- my home page name
- - some page
- - - some sub page
- - sub folder
- - - some sub page
- - sub folder
- - - some sub page
Error when trying to load newly (incorrectly) created page is:
An error occurred while processing your request.
After a pointer from @drobar it seems that Umbraco is ignoring:
<add key="umbracoHideTopLevelNodeFromPath" value="true" />
But only in *some sections. Other sections (same level down, same doc type) new content being created correctly.
Any ideas?
I think it could happen if you've updated the value of that key after the pages have been published, so the links won't get updated until you've republished the entire site (which would also be the solution in your case). Right click any top level node (childs of 'Content') and perform a publish and additionally, right click 'Content' node and choose Republish entire site.
Cheers,
/Dirk
Gave up. Recreated top page and moved all child content across. no problems now.
Just wanted to come back to say that this problem reared its ugly head again recently... And your fix fixed it. Cheers!
I think it didn't work the first time round because there were (somehow) nodes with the same name with the same parent. Not sure how that happened. That was killing the 'republish'.
is working on a reply...