I've been testing umbraco 4.6.1 and have come across a few issues (not sure if these are to do with my system)
This is using IIS 7.5 on Windows 7 .Net 4
Every level 1 node seems to getting a Url of '/'. If both umbracoUseDirectoryUrls (web.config) & addTrailingSlash (umbracoSettings) are set to true then this becomes '//' which isn't valid and the link will fail if returned by NiceUrl in Xslt navigation.
Example structure :-
Content -Home (will always have Url of '/' or '//'. Even setting umbracoUrlName has no effect) --Section 1 --Section 2 --Section 3
Even another page created at the same level as 'Home' get a url of '/' or '//'.
Also posted at cp earlier this week (http://umbraco.codeplex.com/workitem/29900) (although this is the first ticket I've created at cp so maybe it wasn't tagged correctly).
umbracoUseDirectoryUrls & addTrailingSlash
Hi,
I've been testing umbraco 4.6.1 and have come across a few issues (not sure if these are to do with my system)
This is using IIS 7.5 on Windows 7 .Net 4
Every level 1 node seems to getting a Url of '/'. If both umbracoUseDirectoryUrls (web.config) & addTrailingSlash (umbracoSettings) are set to true then this becomes '//' which isn't valid and the link will fail if returned by NiceUrl in Xslt navigation.
Example structure :-
Content
-Home (will always have Url of '/' or '//'. Even setting umbracoUrlName has no effect)
--Section 1
--Section 2
--Section 3
Even another page created at the same level as 'Home' get a url of '/' or '//'.
Is anyone else getting this?
I've got the same problem, but with # as my urls instead of "/".
Have you been able to correct it ?
If the link to document is staying at # when you publish then I think this is a different issue.
Is the node actually getting published? (check umbraco.config in App_Data). I think this is ususally a permissions problem please see this post
I am experiencing the exact same problems...
Submit to cp and we'll have a look for 4.6.2 next week!
Done, thanks Niels :-)
http://umbraco.codeplex.com/workitem/29934
Also posted at cp earlier this week (http://umbraco.codeplex.com/workitem/29900) (although this is the first ticket I've created at cp so maybe it wasn't tagged correctly).
Oops, then I just created a duplicate... *shame*
is working on a reply...