Just don't want to repeat myself, but I can't use any new templates that are created, seems that the there is a UrlAlias assigned to the Content Document Type and even if I create a new Document Type with the same property UrlAlias, it does not render the page, but instead gives me a 404 Error. This has to be custom coding, which I provided in the question on Stack Overflow. But where do I look to find out why I can't add a template and use it??
Could you ellaborate a bit more on your setup? What version of Umbraco are you using and are you using MSSQL and IIS? What version of IIS? Have you done any API integration in Umbraco or on the site?
Has it been acting up like this all the time or has it just began recently?
Hello Jan, I solved the problem. I was using urlAlias, instead of umbracoUrlAlias for the URL's property of that document type and that's why it didn't work.
Created Template, but it's useless and get 404 Error on page url instead... How to unblock it?
I asked this question on stackoverflow, located here: http://stackoverflow.com/questions/22524400/creating-a-template-in-umbraco-but-how-to-unblock-it-instead-i-get-404-error-o
Just don't want to repeat myself, but I can't use any new templates that are created, seems that the there is a UrlAlias assigned to the Content Document Type and even if I create a new Document Type with the same property UrlAlias, it does not render the page, but instead gives me a 404 Error. This has to be custom coding, which I provided in the question on Stack Overflow. But where do I look to find out why I can't add a template and use it??
Any help is greatly appreciated!
Hi Charles
Could you ellaborate a bit more on your setup? What version of Umbraco are you using and are you using MSSQL and IIS? What version of IIS? Have you done any API integration in Umbraco or on the site?
Has it been acting up like this all the time or has it just began recently?
Looking forward to hearing from you.
/Jan
Hello Jan, I solved the problem. I was using urlAlias, instead of umbracoUrlAlias for the URL's property of that document type and that's why it didn't work.
Cheers :)
Hi Charles
Happy to hear you got it figured out :)
/Jan
is working on a reply...