Hi,

 

I have the following problem. When I insert an existing unordered list (<ul>) into CuteEditor it reformats this list so that none of the list items (<li>) are closed, which they originally were. I input the original HTML in the HTML view, then switch to Normal view. If I switch back again to HTML view, all closing tags for the list items (</li>) are gone. This also happens when I insert the HTML in the HTML view, switch to Normal view, and then insert the contents into the database. The HTML in the database then does not contain </li> tags. It does not happen when I insert HTML in in the HTML view and then insert into the database, without switching to Normal view.

I have set the DisableAutoFormatting property of the editor to True because I already had some problems before with rewritten HTML. Can anyone help me?

 

Thanks,

 

Peter

Hello Adam,

 

I'm using version 5, don't know about the .2 though. Anyway, I had the same problem on your example page. Inserted html in the HTML view in correct (validated) xhtml format. After viewing the result in Normal view and switching back to HTML view all the </li> were gone except for the last one. I've tried removing <br/> from list items, reducing the amount of list items etc. (don't ask me why, just trying anything) but the problem remains.

 

I've just been fiddling around some more and I found out that CuteEditor also strips the closing slash from empty elements like <img>, <br> and <input> (<img src="something" />, <br />, etc.).

After searching a little further  I tried your demo on http://cutesoft.net/example/xmloutput.aspx. On this page it seems to work fine. That is, the </li>'s are still gone after switching from Normal to HTML view, but after submitting the page, the code that is returned is correct. Mind you, that is not the behaviour on my website. When submitted to the database, the closing tags are gone from the html found in the database.

 

I suppose there is some setting for CuteEditor to output xhtml, but I couldn't find it. Can you tell me where it is?

 

Thanks.

 

Peter

 

 

Peter,

 

Please use Editor.XHTML Property instead of Editor.Text property.

 

Editor.XHTML Property
Retrieves the CuteEditor HTML content in XHTML format.

 

>>I've just been fiddling around some more and I found out that CuteEditor also strips the closing slash from empty elements like <img>, <br> and <input> (<img src="something" />, <br />, etc.).

 

That's the IE behaviour.  The only solution is using  Editor.XHTML Property extract data from Cute Editor. Cute Editor will fix those problems in the server side.

 

There are many improments and changes since version 5.0.

 

 

I suggest you upgrade to the latest version. It's a free upgrade.

 

 

Keep me posted.

 

 

 

 

This is interesting because I just noticed the same problem with the editor appearing to not close <dt> tags. After editing some content, all my </dt> tags were gone!

 

You said: "That's the IE behaviour" and, indeed, when I use the editor in Firefox it does seem to behave differently (the </dt> tags did not get stripped).

 

Would you classify this as a bug that you can fix in a later version?

 

You also suggested using the Editor.XHTML property to work around the problem. This is not a satisfactory workaround for me because I was data binding to the Editor.Text field which is read/write. I can't bind to the Editor.XHTML property without writing extra code because it is read-only.

 

Any chance you'll make the Editor.XHTML property read/write in a later version?

 

Thanks.

 

(I'm only using the trial version right now while I evaluate which editor to use on my site.)

Hi Adam,

 

I've tried using the Editor.XHTML property to retrieve the CuteEditor HTML content in XHTML format. This property also returns the list without the closing </li> tags (so in fact returns invalid XHTML). I've upgraded to version 5.2 but no change. I've tried binding the editor.xhtml property to a literal control to check if something went wrong when inserting into the database, but the literal showed the same thing, unclosed <li> tags and also unclosed <br> tags. So it would seem that the xhtml property does not fix the problems. I'm aware though that on the demo you mentioned above it works fine. So what else could I be doing wrong?

 

Peter