I'm fairly sure that you can't use spaces in your url's per default. When you publish a document in Umbraco, it will give you an url like /a-nother and AFAIK Umbraco wont match /a nother
Its not the URL that has the space, its the page name. For example, on my own Umbraco site:
http://www.aurl.com/web-design.aspx : works fine and the page name property is "web design" which is getting translated into web-design.aspx just fine.
@Jan - no modifications that I know of. The config looks as per normal to me:
Ok, turns out its not so odd, and that I'm being a bit slow this week!
When I created my doctype, it didnt have a matching template - this is what is causing the error. I dont have a technical explanation but re-creating the docType with a matching template has worked.
Very odd URL error
Hi,
I'm using 4.7 and have a weird problem with URLs.
Anything with a space in (eg. "a nother") causes a 404 error:
umbraco tried this to match it using this xpath query'/root/* [@urlName = "a-nother"] | /root/*/* [@urlName = "a-nother"]')
Does anyone have any ideas as to why this could be happening.
Thanks in advance.
Hi Greyhound
Do you know if there has been done some modification to the umbracoSettings.config?
What does your <urlreplacing></urlreplacing> section look like?
/Jan
I'm fairly sure that you can't use spaces in your url's per default.
When you publish a document in Umbraco, it will give you an url like /a-nother and AFAIK Umbraco wont match /a nother
/Mads
Yes, Mads is right about that.
/Jan
Hi,
Its not the URL that has the space, its the page name. For example, on my own Umbraco site:
http://www.aurl.com/web-design.aspx : works fine and the page name property is "web design" which is getting translated into web-design.aspx just fine.
@Jan - no modifications that I know of. The config looks as per normal to me:
Ok, turns out its not so odd, and that I'm being a bit slow this week!
When I created my doctype, it didnt have a matching template - this is what is causing the error. I dont have a technical explanation but re-creating the docType with a matching template has worked.
Thanks for the replies.
Hi Greyhound
Ah yes, missing templates can fool one :) Glad to see you got it solved.
/Jan
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.