Thread

Hi all,

After upgrading to EE 2.1.3 a test installation with a copy of my productive database, I recognized that EE doesn’t convert back encoded HTML entities when I open a channel entry for modifying.
Means that in my input textarea for the field “text” are signs showing up like

ö

and so on.

Do I have to set any special character encodings in my EE 2.1 installation? Or any special settings on the field?
This was a 1:1 migration from EE 1.6.7 to EE 2.1.3.

Thanks for giving some hints 😉
Simon

Hi, Simon. What encoding were you using in your database for 1.x? Are you using UTF-8 for your templates?

Ok, I think there’s the point:
All my EE 1.x tables have latin1_german1_ci as collation and in EE 2.x they’re on utf8_general_ci.

In this case: What’s the best practive for upgrading? Is there a way to perform a proper conversion from latin1 to utf8?

Sue,

I made some additional tests:
Before upgrading to 2.x I converted all tables to utf8_general_ci with

ALTER TABLE <table> CONVERT TO CHARACTER SET utf8

and the database with

ALTER DATABASE  <db> DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci

I also tested if characters show up correct in 1.x then I upgraded to 2.x and still have those encoded html entities.

Actually templates do not have an impact because I’m only looking at the EE backend.

Was that a regular upgrade? EE should do the necessary db conversion for you.

Absolutely. I cloned db & EE installation (and applied new URLs and paths) and started migration from there. But still on the samer server with same character sets on db and connection.

Simon,

Just to confirm. Your ö character is showing in ascii or literally in your EE1.x textarea? What does it look like in your EE1.x db?

In your EE1.x weblog preferences for that weblog what do you have set for Default HTML formatting in weblog entries?

Also in your Global weblog preferences what did you have set for the convert ascii setting?

Hey John,

Exactly. The ö character in the db of my EE1.x installation is in ascii and in the extarea literally.
In the db of EE2.x, the character is still ascii but also in the textarea.

“Default HTML formatting in weblog entries” is set to “Allow ALL HTML”.
In my global weblog preferences, I’ve set to convert special characters automatically to html entities.

HTH.

Hi Simon,

This may be a bug. Let me confirm with the development team.

Thanks!
Barry

Hey barry
Any news on that?
Thanks
Simon

Simon, I pinged the devs for you again. There may be as there was, some delay as they are all in Dallas at the moment on training.

Hi All,
sorry for bother you again, but did you already got an answer from the devs?
This situation is slightly uncomfortable for us because we’d like to upgrade as soon as possible…
Thanks
Simon

Hi Simon,

Unfortunately not yet. Thank you for you patience.

Cheers

Greg

Could please anybody give an update?
It’s going to get exhausting 😕

Thanks
Simon

Simon,

Your thread has been escalated internally and any updates from the devs will appear here as a reply. Thanks for your patience.