Hi Zafer,

Usually when people report issues like this it turns out to be database characterset related, but this case sounds different in that you say it works ok in the blog. When I look at your site it looks like there are non-english characters in your home page (HtmlContent module). Are you saying it only happens for new content? Did it work correctly before the upgrade?

What data layer are you using?

What characterset and collation is used in your db?

If you look at the properties of the mp_HtmlContent table do you see any difference in charset or collation vs the mp_Blogs table?

Thanks,

Joe

Hi Zafer,

Do you know what version you had before the upgrade?

There is a setting in Web.config:

<globalization
culture="auto:en-US"
uiCulture="auto:en"
requestEncoding="utf-8"
responseEncoding="utf-8"
fileEncoding="iso-8859-15" />

Did you previously have this customized? Maybe the new Web.config overwrote your settings? This setting really should not affect it but still might be related.

NText should be the correct data type for storing multi lingual text so it sounds correct for both tables.

I can't see any reason the HtmlContent module should behave any differently than the blog. I've reviewed the code and nothing jumps out at me.

Joe

One thing I can think of that is different between the blog and the htmlcontent module is that by default blog isn't cached and html is. I can't think of why this would make a difference but grasping for ideas.

If you click the gear icon next to the title of your htmlcontent instance, then you will see the default cahce time is probably 360. Try setting it to 0 then edit the content and see if it makes any difference.

Joe

Hi Zafer,

I'll keep pondering it here as well. If you could send me a utf encoded file like an html file or something with content in turkish that I can use to try and re-create the problem here it would help. If I can produce the problem here I can surely fix it.

Another epxeriment to try is changing the editor and see if it makes any difference. i.e if you are using FCKeditor try using TinyMCE or if you are using TinyMCE try using FCKeditor and see if that makes a difference. I would also try editing with different browsers IE7 and Firefox and see if result is the same in both or if its isolated to a specific browser.

Thanks,

Joe