Support forums » Products » Cute Editor for .NET » Re: Normal View encoding URLs

Normal View encoding URLs

Last post 02-23-2009, 3:23 PM by Adam. 1 replies.
Sort Posts: Previous Next

  •  02-23-2009, 3:16 PM 49130

    Normal View encoding URLs

    Reply Quote
    When switch from HTML view to normal view then back the src tag of our Iframes is being encoded and the &'s seperating the query params are being turned into &
     
    ex..
     
    before
    <iframe src="http://cutesoft.net/path/File.aspx?param1=asdf&param2=ghjk" frameborder="0" width="360" scrolling="no" height="275"></iframe>
     
    after
    <iframe src="http://cutesoft.net/path/File.aspx?param1=asdf&amp;param2=ghjk" frameborder="0" width="360" scrolling="no" height="275"></iframe>
     
    It happens during the switch to normal view because if you look at the uiCuteEditor.Text value before switching to normal it has the correct value.  But if you look at it after switching to normal it has the escaped value.
     
    The control is embeded on the page with these settings.
    <CE:Editor ID="uiCuteEditor" runat="server" AllowEditServerSideCode="True"
                        EditorBodyStyle="internal" EnableStripIframeTags="False"
                        EnableStripLinkTagsCodeInjection="False"
                        EnableStripStyleTagsCodeInjection="False" RemoveTBODYTag="True"
                        StyleWithCSS="True" EnableStripScriptTags="False">
    <FrameStyle BackColor="White" BorderColor="#DDDDDD" BorderWidth="1px" BorderStyle="Solid" CssClass="CuteEditorFrame" Height="100%" Width="100%"></FrameStyle>
                    </CE:Editor>
     
    In the code behind we are also setting
    uiCuteEditor.URLType = URLType.SiteRelative


    I would like to be able to disable this feature.

    Thank You
    Andrew Taft

  •  02-23-2009, 3:23 PM 49134 in reply to 49130

    Re: Normal View encoding URLs

    Reply Quote
    Andrew,
     
    Please set the following property to true.
     

    Editor.UseSimpleAmpersand Property

    W3C recommend that all '&' in query strings be converted to &amp; This is the only way to get a piece of HTML validated. The reason is that & is the start of an HTML entity, such as &pound;

    So this: 

                
            <a href="page.aspx?var1=one&amp;va­r2=two">link</a> 
    is valid, whereas: 
            <a href="page.aspx?var1=one&var2=t­wo">link</a> 
    isn't.
    If you still want to use simple Ampersand in query strings, you can set this property to true. if you want to retrieve the CuteEditor HTML content in XHTML format, the 'UseSimpleAmpersand' property will be ignored.
     
    Demo:
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx
View as RSS news feed in XML