I got a documenttype Voorwaarden and the name of the page is Voorwaarden2 but when i type the url of the documenttype name in de url it goes to the root of the site.
The short version is that Umbraco is rendering your homepage content with your Voorwaarden template. You can disable that behavior (see above link for details).
Is this normal routing?
Hi all,
I got a documenttype Voorwaarden and the name of the page is Voorwaarden2 but when i type the url of the documenttype name in de url it goes to the root of the site.
So the normal url is https://localhost:44300/voorwaarden2/ But when i use the documenttype name as url https://localhost:44300/voorwaarden/ it goes to the root of the site.
I would expect a 404 error. Is this behavior correct? Can someone explain this?
BTW this is what i find in the log files: EBUG Umbraco.Web.Routing.PublishedContentRequestEngine - FindDomain: Uri="https://localhost:44300/voorwaarden" DEBUG Umbraco.Web.Routing.PublishedContentRequestEngine - FindDomain: Matches no domain DEBUG Umbraco.Web.Routing.PublishedContentRequestEngine - FindDomain: Culture="nl-NL" DEBUG Umbraco.Web.Routing.PublishedContentRequestEngine - FindPublishedContentAndTemplate: Path="/voorwaarden" DEBUG Umbraco.Web.Routing.PublishedContentRequestEngine - FindPublishedContent: Begin finders DEBUG Umbraco.Web.Routing.ContentFinderByNiceUrl - Test route "/voorwaarden" DEBUG Umbraco.Web.Routing.ContentFinderByNiceUrl - No match. DEBUG Umbraco.Web.Routing.ContentFinderByIdPath - Not a node id DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Registering custom handlers. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Configured: 'umbraco.SearchForAlias,umbraco'. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Registering 'umbraco.SearchForAlias'. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Configured: 'umbraco.SearchForTemplate,umbraco'. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Registering 'umbraco.SearchForTemplate'. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Configured: 'umbraco.SearchForProfile,umbraco'. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Registering 'umbraco.SearchForProfile'. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Configured: 'umbraco.handle404,umbraco'. DEBUG Umbraco.Web.Routing.NotFoundHandlerHelper - Registering 'umbraco.handle404' as "last chance" handler. DEBUG Umbraco.Web.Routing.ContentFinderByNotFoundHandlers - Running for legacy url='voorwaarden'. DEBUG Umbraco.Web.Routing.ContentFinderByNotFoundHandlers - Handler 'umbraco.SearchForAlias'. DEBUG Umbraco.Web.Routing.ContentFinderByNotFoundHandlers - Replace handler 'umbraco.SearchForAlias' by new finder 'Umbraco.Web.Routing.ContentFinderByUrlAlias'. DEBUG Umbraco.Web.Routing.ContentFinderByNotFoundHandlers - Handler 'umbraco.SearchForTemplate'. DEBUG Umbraco.Web.Routing.ContentFinderByNotFoundHandlers - Replace handler 'umbraco.SearchForTemplate' by new finder 'Umbraco.Web.Routing.ContentFinderByNiceUrlAndTemplate'. DEBUG Umbraco.Web.Routing.ContentFinderByNiceUrlAndTemplate - Valid template: "voorwaarden" DEBUG Umbraco.Web.Routing.ContentFinderByNiceUrl - Test route "/" DEBUG Umbraco.Web.Routing.ContentFinderByNiceUrl - Got content, id=1052 DEBUG Umbraco.Web.Routing.ContentFinderByNotFoundHandlers - Finder 'Umbraco.Web.Routing.ContentFinderByNiceUrlAndTemplate' found node with id=1052. DEBUG Umbraco.Web.Routing.ContentFinderByNotFoundHandlers - Handler 'umbraco.SearchForTemplate' found valid node with id=1052.
Probably a result of the "alternative templates" feature of Umbraco. See here: https://our.umbraco.org/forum/templates-partial-views-and-macros/77715-umbraco-7-template-rending-as-web-pages#comment-248526
The short version is that Umbraco is rendering your homepage content with your Voorwaarden template. You can disable that behavior (see above link for details).
The setting in the unmbraco.config didn't do the trick. But disable the line in the 404handlers.config works!
Thnx Nicholas!
is working on a reply...