Your diagnosis was correct. In moving the site to the new host the valid license was inadvertently overwritten by the trial license. The latter has now been deleted, shredded and cast into the wilderness. It's reassuring to know that a server change does not invalidate the license. Thanks

We changed hosts and the CuteSoft license file was inadvertently overwritten by the trial version. It appeared to us as if the license did not transfer to another host. The error broke the site. It took almost eight hours to get a response to a trouble ticket. .

We migrated a site to a new server - same domain name. Any attempt to open a page that uses your product produces the error: The License for Editor is not valid. You are using a trial license and the trial period has expire.  And how to fix please?

For some odd reason the validator example doesn't work in my DetailView. It isn't a major issue; I catch it in code behind.

I looked at the code in editor-onpaste.aspx.   I added the following code but the result is the same: none of the Word markup is removed and the item is no longer editable.   Editor newsEditor = ((Editor)NewsView.FindControl(''CeNews'')); newsEditor.EditorOnPaste = PasteBehavior.PasteWord;

What does EditorOnPaste do? Whether I set it to EditorOnPaste = ''PasteWord'' or EditorOnPaste = ''PasteText'' the result if a user pastes from a Word document directly into the editor is that I get all the Word garbage. Is there a setting that will allow the user to paste directly from a Word document that will strip out all the Word ...

is there an example of the code necessary to limit the length of the text entered in the editor?

Is anyone doing this? I tried but not only does the validator not fire but the submit button gets killed.

Here's some code for getting rid of the unwanted IE <p> tags. It's a bit of a pain but, in my case, necessary. In this example the ''Name'' string is coming from an Editor control in a details view:   string name_p2 = ((Editor)EventView.FindControl(''CeName'')).Text; // Clean the unwanted <p></p> tags that IE ...

This is an example of some obvious browser compatibility bugs. Will they be fixed?   Here's a comparison of how the two browsers handle Cute entries. Versions IE 7 and Firefox 3   TEST ONE:  BreakElement=''P''   IE encloses each line in opening and closing <p> tags Firefox does the same   TEST TWO  ...