I've only recently downloaded the trial version for testing and I really like what I see. The product seems very flexible and customisable. My compliments!

 

However, on my test page I run into a problem when I set Editor1.Text to the value of a memo field from a record in my database.
It doesn't matter which record I try to edit, the error is always: "An invalid character was found in text content"

 

What's wrong?

 

BTW, it's a client-side JavaScript error.

MajaR,

 

Can you check the following example?

 

 

 

The source code of this example can be found in the download package.

 

You can modify it to meet your requirements.

 

Keep me posted

I've tried that and the base page did not have this error.

 

But the example page uses a very basic editor, so I gradually added some configuration options that I use in my own test page.

That's how I found out that the error occurs when I set: CustomCulture="nl-NL"

Any ideas on how to prevent this error?
At this point we're still only evaluating the CuteEditor, but it is useless for us if we can't set it's language to Dutch without getting errors.

This turned out to be an encoding issue. I had the following line in my web.config file:

<globalization enableClientBasedCulture="true" culture="nl-NL" uiCulture="nl-NL" requestEncoding="ISO-8859-15" responseEncoding="ISO-8859-15" fileEncoding="iso-8859-15" />

Changing that to: 
<globalization enableClientBasedCulture="true" culture="nl-NL" uiCulture="nl-NL" />
solved the issue.

Hi,

 

We have the same issue.

When adding responseEncoding="ISO-8859-1" to the web.config globalization  the "invalid character was found in text content" message starts to appear every time an editor is loaded. This is a major issue since removing the responseEncoding messes up our site completely.

 

Is there anyway to set the editor to the same encoding or some other way to get rid of the error message?

 

Regards Chris