We have an issue where a doctype (the docType used by the home page ) loses its Default and Allowed Templates when you publish a page that uses that DocType.
After this happens the page does not have a template and results in a 404.
It can be resolved by going back to the DocType and selecting the template, the page then has its template restored, so you can publish the page and everything works again.
This is only happening to one DocType in the site, and of course only happens intermittently - not every time you publish.
I have managed to narrow down the cause, such that I can recreate the issue.
The Home Doctype is losing its Default Template and Allowed Templates when the App Pool recycles. I can look at the DocType and see that it has a template. If I then manually recycle the App Pool and refresh the DocType settings all the template info is gone.
This explains the intermittent nature of the problem. It is only noticeable on the first publish after the App Pool recycles. The publish is not involved with the problem except for bringing it to our attention.
Document Type Forgets Template
Hi
We have an issue where a doctype (the docType used by the home page ) loses its Default and Allowed Templates when you publish a page that uses that DocType.
After this happens the page does not have a template and results in a 404.
It can be resolved by going back to the DocType and selecting the template, the page then has its template restored, so you can publish the page and everything works again.
This is only happening to one DocType in the site, and of course only happens intermittently - not every time you publish.
We are using Umbraco 4.11.4 with MVC.
Has anyone seen this before?
Thanks
Dallas
I have managed to narrow down the cause, such that I can recreate the issue.
The Home Doctype is losing its Default Template and Allowed Templates when the App Pool recycles. I can look at the DocType and see that it has a template. If I then manually recycle the App Pool and refresh the DocType settings all the template info is gone.
This explains the intermittent nature of the problem. It is only noticeable on the first publish after the App Pool recycles. The publish is not involved with the problem except for bringing it to our attention.
Dallas
is working on a reply...