4.3 and 4.2 issue -- URL's with periods in them.

Posted by Community Admin on 04-Aug-2018 22:46

4.3 and 4.2 issue -- URL's with periods in them.

All Replies

Posted by Community Admin on 01-Dec-2011 00:00

Whenever we create a page with a period in the title (which then defaults to be a period in the generated URL), the page cannot be edited in sitefinity control panel and cannot be viewed online in the front end either.

Example page title:  "Lottery winner receives $1.1 million".

the default url that DOESNT work:
~/somefolder/lottery-winner-receives-$1.1-million

This DOES work (no period in the 1.1)
~/somefolder/lottery-winner-receives-$11-million


Upgraded to latest version of sitefinity this morning just incase it would help, no luck.

Any tips other than telling client to manually remove periods?

thanks,

Chris

Posted by Community Admin on 01-Dec-2011 00:00

I should also mention that i've tried this on multiple sitefinity sites of ours, and it happens on all of them that i tried (ranging from 4.2 to 4.3)

thanks!

Posted by Community Admin on 02-Dec-2011 00:00

Hello Chris Hayward,

The special symbols are forbidden in 4.3 due to some issues in earlier versions of Sitefinity. However we know of an issue with the fullstop, as you show in your example - if you use it between two strings, the page will generate a 404 error, which prevents you from further editing it.

We have this issue logged in our system for fixing, so you can expect it to be fixed in one of our future releases. Unfortunately there is no workaround for that issue other than removing the periods. We are sorry for the caused inconvenience.

Greetings,
Victor Velev
the Telerik team

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 05-Dec-2011 00:00

Dear Victor

Maybe you have a solution internal already since a similiar case seemes to have been fixed: http://www.telerik.com/support/pits.aspx#/public/sitefinity/7673

Markus

Posted by Community Admin on 06-Dec-2011 00:00

Hello Markus,

The issue you speak of is different one which occurred in 1650 and was later fixed in 4.3.

However the problem Chris reported is also fixed in one of our latest internal builds, so it will be included in the official 4.4 release.

Regards,
Victor Velev
the Telerik team

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

This thread is closed