This is in place as the most common approach to content tree setup is
Content - Website -- Home
This makes traversing the xml tree structure via xslt much easier
(trust me). It also supports multi-site or multi-language easier.I would recommend moving to the above structure and laeving the appsetting as is.
The reason http://locahost/homepage.aspx works is due to 'alternative templates'. Any page can be requested, but an alternative template applied. In your example the homepage is requested, with the 'alternative' template of homepage (which was the original template, but this doesn't matter).
Thank you for your reply. I changed the structure to: Content - Website -- Home --- News
And I left "umbracoHihdeTopLevelNodeFromPath" on true. The hostname "localhost" is set to Home. Now when I go to http://localhost I get the correct page. If I go to http://localhost/home.aspx I get the 404-page (of .Net, not Umbraco) If I go to http://localhost/home/news.aspx I get the correct page (http://localhost/news.aspx doesn't work). I accidentally types http://localhost/homeews.aspx and then I get the Umbraco "page not found" (umbraco tried this to match it using this xpath query'/root/node [@urlName = "homeews"] | /root/node/node [@urlName = "homeews"]')
I really don't see what I'm missing. Do you have any other suggestions?
home.aspx generates 404
Hello, I'm new to Umbraco and I'm having the following problem:
If I go to http://localhost I get the right page.
If I go to http://localhost/home.aspx I get a 404.
"Home" is the first node in my contenttree. The template of home is "homepage".
If I go to http://localhost/homepage.aspx, it works.
http://localhost/Default.aspx?umbPage=home also works.
I published the whole site.
I don't know what I'm missing.
Your help is appriciated.
Thanks in advance.
Kind regards, Jeroen
Hi Jeroen,
There is a web.config appsetting that hides the top level node from displaying. Try changing this to false an it should work.
This is in place as the most common approach to content tree setup is
Content
- Website
-- Home
This makes traversing the xml tree structure via xslt much easier (trust me). It also supports multi-site or multi-language easier.I would recommend moving to the above structure and laeving the appsetting as is.
The reason http://locahost/homepage.aspx works is due to 'alternative templates'. Any page can be requested, but an alternative template applied. In your example the homepage is requested, with the 'alternative' template of homepage (which was the original template, but this doesn't matter).
Hi Chris,
Thank you for your reply.
I changed the structure to:
Content
- Website
-- Home
--- News
And I left "umbracoHihdeTopLevelNodeFromPath" on true.
The hostname "localhost" is set to Home.
Now when I go to http://localhost I get the correct page.
If I go to http://localhost/home.aspx I get the 404-page (of .Net, not Umbraco)
If I go to http://localhost/home/news.aspx I get the correct page (http://localhost/news.aspx doesn't work).
I accidentally types http://localhost/homeews.aspx and then I get the Umbraco "page not found" (umbraco tried this to match it using this xpath query'/root/node [@urlName = "homeews"] | /root/node/node [@urlName = "homeews"]')
I really don't see what I'm missing.
Do you have any other suggestions?
Can you try changing the home page title (e.g. home2)?
What does the link at the bottom of the the Property tab show?
You should be receiving the same error for home.aspx as homeews.aspx. Can you check that the following appsettings keys are identical to
The reservedpaths/urls keys inform umbraco to not try and match content nodes to certain urls.
is working on a reply...