I have a site that I have been running on my local IIS with no problem, and I recently did a push to our staging server environment as well. Both of these environments are pulling the data from the same Umbraco database, but suddenly today I can't access one of the nodes of the site locally.
On the staging site I can go to 'domain.com/page' and the page loads, but locally if I go to '/page' I get a 404. I can go to all other pages just fine, it's only if I go to '/page or /page/subpage' that it's not found. If I use the preview from within the admin (running locally) I can see the page and all of the content is there, but when actually browsing to the page it gives the 404.
So far I've tried recycling the App Pool, republishing all content from the main root, unpublishing the page and it's descendants then republishing all, and setting the local XmlCache to disabled - none of which are working.
When you say that you unpublished and then published all, do you mean that you did the "Republish the entire site"? Or did you right click on the specific node and select Publish in the context menu? Republishing the entire site is more of a light publish, and you probably want the one in the context menu.
I would also try reindexing your examine indexes and checking in the App_Data\Logs\umbracoTraceLog.txt to see if there are any errors being thrown that are preventing the node from being published. Maybe there are file permissions?
Are you able to unpublish and republish other nodes on your local site and have them still work? Verify that when you unpublish a node locally, that it actually gives you a 404, and then verify that you can publish it again.
Do you see the node in question in the xml cache on disk at App_Data\umbraco.config?
I did both - republished the entire site and unpublished/published the node in the context menu. Looking at the Trace Log, I think it looks like Umbraco thinks there is a different node ID for the root node in my local environment:
When I look at the content properties for the page at /business, it now says the ID is 1208. Looking in the umbraco.config file, it is also showing up there but it has an id of 1073 - which is what it was initially before unpublishing and then republishing. All of the subpages for business also show the path being based on 1073. For example:
What's really strange is that it all works in my staging server environment! Can I manually replace 1073 with the new ID of 1208 for everything, or is there a way to get the parent node page (/business) to be 1073 again?
I can unpublish and republish other sections/pages with no problem, and the ID doesn't change on them. It's only this one giving me a problem.
File or directory not found
I have a site that I have been running on my local IIS with no problem, and I recently did a push to our staging server environment as well. Both of these environments are pulling the data from the same Umbraco database, but suddenly today I can't access one of the nodes of the site locally.
On the staging site I can go to 'domain.com/page' and the page loads, but locally if I go to '/page' I get a 404. I can go to all other pages just fine, it's only if I go to '/page or /page/subpage' that it's not found. If I use the preview from within the admin (running locally) I can see the page and all of the content is there, but when actually browsing to the page it gives the 404.
So far I've tried recycling the App Pool, republishing all content from the main root, unpublishing the page and it's descendants then republishing all, and setting the local XmlCache to disabled - none of which are working.
Any ideas on what this could be?
Thanks!
When you say that you unpublished and then published all, do you mean that you did the "Republish the entire site"? Or did you right click on the specific node and select Publish in the context menu? Republishing the entire site is more of a light publish, and you probably want the one in the context menu.
I would also try reindexing your examine indexes and checking in the
App_Data\Logs\umbracoTraceLog.txtto see if there are any errors being thrown that are preventing the node from being published. Maybe there are file permissions?Are you able to unpublish and republish other nodes on your local site and have them still work? Verify that when you unpublish a node locally, that it actually gives you a 404, and then verify that you can publish it again.
Do you see the node in question in the xml cache on disk at
App_Data\umbraco.config?Hi Mark,
I did both - republished the entire site and unpublished/published the node in the context menu. Looking at the Trace Log, I think it looks like Umbraco thinks there is a different node ID for the root node in my local environment:
When I look at the content properties for the page at /business, it now says the ID is 1208. Looking in the umbraco.config file, it is also showing up there but it has an id of 1073 - which is what it was initially before unpublishing and then republishing. All of the subpages for business also show the path being based on 1073. For example:
What's really strange is that it all works in my staging server environment! Can I manually replace 1073 with the new ID of 1208 for everything, or is there a way to get the parent node page (/business) to be 1073 again?
I can unpublish and republish other sections/pages with no problem, and the ID doesn't change on them. It's only this one giving me a problem.
Alright, I manually updated the Xml field in the database and the config file, but it is still trying to load the page at an absolute URL:
If I click in to another section that isn't having a problem, I get a standard path:
I don't see where it would be getting an absolute URL from on the business pages?
is working on a reply...