More in this section
Forums / Bugs & Issues / News Title with special characters too long

News Title with special characters too long

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.
2 posts, 0 answered
  1. Mike
    Mike avatar
    208 posts
    10 Dec 2007
    30 Apr 2010
    Link to this post
    This one is a bit weird.  We happen to have a long news article title, but it is well under 256 characters.  I found that using "extended" characters such as smart quotes and m-dash, the title seems to be much longer than the actual number of character to Nolics, and I get the following error:


    Server Error in '/' Application.

    Value for property Url is too long. Maximun length is 256
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: Nolics.ORMapper.Base.LengthException: Value for property Url is too long. Maximun length is 256

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

    Stack Trace:

    [LengthException: Value for property Url is too long. Maximun length is 256]
       Telerik.Cms.Engine.Data.CmsContentBase.nn_verifyData() +353
       Telerik.Cms.Engine.Data.CmsContentBase.Nolics.ORMapper.Base.IOdbClass.BeginCommit() +22
       Nolics.ORMapper.Base.Transaction.Commit(Boolean fCleanIfSuccess) +910
       Nolics.ORMapper.Base.Transaction.Commit() +10
       Telerik.Cms.Engine.Data.Providers.DefaultProvider.SaveContent(IContent content, Boolean fireEvents) +403
       Telerik.Cms.Engine.ContentProviderBase.SaveContent(IContent content) +12
       Telerik.Cms.Engine.ContentManager.SavedStagedContent(StagedContent staged, ContentStatus status) +257
       Telerik.Cms.Engine.ContentManager.SaveContent(IContent content, ContentStatus status) +1267
       Telerik.Cms.Engine.WebControls.Admin.ContentItemEdit`1.SaveContent() +1211
       Telerik.Cms.Engine.WebControls.Admin.ContentItemEdit`1.Button_Command(Object sender, CommandEventArgs e) +62
       System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e) +108
       System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +135
       System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
       System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
       System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +175
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565



    Here is an example URL that is 223 characters long (but with two smart quotes and one mdash): 
    12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890test “this string”—here

    The smartquotes were entered using alt-0147 and alt-0148 and the m-dash using alt-0151. If you shorten it to 222 characters, it works fine.  Here's what's weird:  If you replace the m-dash with the HTML entity — then it works fine. 

    So, if I stick with the m-dash (entered as alt-0151), I get the error when I enter only 28 of them, as in this example:


    What's even weirder is that I can add 28 alt-0151 m-dash characters in a generic content title, but #29 causes the error.

    Obviously, this isn't a show-stopper, but I thought you might like to know.  :) 

    Mike Sharp

  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    12 Sep 2017
    02 May 2010
    Link to this post
    Hello Mike,

    The special chars are not parsed as a regular alpha numeric chars. You could use separate a metakey which value type is long text to get around this issue.

    Best wishes,
    Ivan Dimitrov
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
2 posts, 0 answered