I've deleted the umbraco.config file and republished each root node as described in the wiki
The output looks like this:
Page not found
No umbraco document matches the url 'http://cp.localhost/'
umbraco tried this to match it using this xpath query'/* [@urlName = "careerplan4me"] | /root/* [@urlName = "careerplan4me"]')
This
page can be replaced with a custom 404 page by adding the id of the
umbraco document to show as 404 page in the
/config/umbracoSettings.config file. Just add the id to the
'/settings/content/errors/error404' element.
Just before xPath query (False, '/* [@urlName = "careerplan4me"] | /root/* [@urlName = "careerplan4me"]')
0,000606094565295034
0,000018
umbracoRequestHandler
pageXPathQueryStart: '/root'
0,000617215566493108
0,000011
umbracoRequestHandler
After xPath query
0,000648867646826088
0,000032
umbracoRequestHandler
Access checking started
0,000676670149821273
0,000028
umbracoRequestHandler
Page not protected
0,000730564232550401
0,000054
umbracoRequestHandler
Access checking ended
0,00074596254190158
0,000015
umbracoInit
Done handling request
0,000757083543099654
0,000011
umbracoPage
testing altTemplate
0,000935875023899459
0,000179
umbracoPage
Element loaded: umbracoPermanentRedirect
0,00101971026370032
0,000084
umbracoPage
Element loaded: keywords
0,00104494638180365
0,000025
umbracoPage
Element loaded: description
0,00107360434642945
0,000029
umbracoPage
Pagedata loaded for careerplan4.me (ID: 1590)
0,00108814719415001
0,000015
umbracoPage
Looking up skin information
0,00112236565937485
0,000034
and for level 2:
Page not found
No umbraco document matches the url 'http://cp.localhost/home'
umbraco tried this to match it using this xpath query'1592')
This
page can be replaced with a custom 404 page by adding the id of the
umbraco document to show as 404 page in the
/config/umbracoSettings.config file. Just add the id to the
'/settings/content/errors/error404' element.
umbraco can't find root and first level nodes after update to new schema
I don't know if this is a xslt issue but the error mentions xpath so...
I've got a site that has been converted to the new schema.
My problem ocours when I try to access the root or level 1 nodes ie:
http://root or http://root/level1
I can access the node on second level
http://root/level1/level2
I've deleted the umbraco.config file and republished each root node as described in the wiki
The output looks like this:
Page not found
No umbraco document matches the url 'http://cp.localhost/'
umbraco tried this to match it using this xpath query'/* [@urlName = "careerplan4me"] | /root/* [@urlName = "careerplan4me"]')
This page can be replaced with a custom 404 page by adding the id of the umbraco document to show as 404 page in the /config/umbracoSettings.config file. Just add the id to the '/settings/content/errors/error404' element.
For more information, visit information about custom 404 on the umbraco website.
This page is intentionally left ugly ;-)
Request Details
Trace Information
and for level 2:
Page not found
No umbraco document matches the url 'http://cp.localhost/home'
umbraco tried this to match it using this xpath query'1592')
This page can be replaced with a custom 404 page by adding the id of the umbraco document to show as 404 page in the /config/umbracoSettings.config file. Just add the id to the '/settings/content/errors/error404' element.
For more information, visit information about custom 404 on the umbraco website.
This page is intentionally left ugly ;-)
Request Details
Trace Information
Hi Kristian
That's really odd. Have you tried restarting the website?
I don't think it has to do with XSLT if you can't access the home page at all when entering the url in the browser.
/Jan
I dont susspect it to be a xslt issue either.
A reset of the website does not change anything
/krisian
Did you republish the website using http://domain.com/umbraco/dialogs/republish.aspx?xml=true after updating to the new xml schema?
Cheers,
/Dirk
No I did not. I've just tried and it does not seem to solve the problem
/kristian
I now got it to work by attaching a template to the Node.
Previously they did not have that and does not need it because we do a 301 redirect.
Anyways that solved it
/kristian
is working on a reply...