Upgrades Questions on upgrading to version 6.x.
Version 6.x > Upgrades > Can't browse with trailing slash while logged into cmsdesk View modes: 
User avatar
Member
Member
mwheel-osa - 11/10/2011 9:10:47 AM
   
Can't browse with trailing slash while logged into cmsdesk
We've upgraded a site from version 5.5.3996 R2 to 6.0.4323.

Issue: If you are logged in to the cmsdesk as an editor and attempt to access a page url with a trailing slash in the same browser but viewing the site outside of cmsdesk you get a 404 error. If you are not logged into cmsdesk as an editor this url will work.

Please note the URLs below are for an internal test site, this site is not yet live so these won't work.

For example when logged in as an editor the following urls work:
http://domain/about_us
http://domain/about_us.aspx

This url however does not work when logged in and will present a 404:
http://domain/about_us/

Prior to the upgrade this site was working properly with extensionless urls and an enforced trailing slash.

We've check through the settings in IIS 7, web.config and the settings in Kentico related to the URL without much luck. Any assistance or ideas would be greatly appreciated.

User avatar
Member
Member
mwheel-osa - 11/17/2011 11:12:43 AM
   
RE:Can't browse with trailing slash while logged into cmsdesk
I worked with Helena via email, for anyone else having this issue it is a known bug.

User avatar
Kentico Developer
Kentico Developer
kentico_ivanat - 11/21/2011 4:02:48 AM
   
RE:Can't browse with trailing slash while logged into cmsdesk
Hi,

here is information for readers of this thread:

After deeper investigation it has turned out that this behavior is not a bug as it might seem to be at the first sight. It is caused by the the slash at the end of the Url specified in the Page not found property.

However, it could be confusing and lead to this kind of situation so we have decided to change it. The next hotfix 6.0.6 should fix this "correct" behavior and even if you specify the slash at the end of page not found Url it should work correctly as you would expect.

Best regards,
Ivana Tomanickova