Thread

I upgraded from 1.6.9 core version to 2.0.2 PB.
After the upgrade completed successfully I’m facing a problem with encoding.
Most of my content in weblogs and template files was in Greek. Every Greek character is presented as question mark now.
My control’s panel charset before upgrade was utf-8.

Thanks in advance

Hi enterweb,

Welcome to the forums!

Is your content rendered as question marks both on the front end and within your channel entries in the CP or is it only on the front end and text that is in the templates?

Cheers

Greg

Hi Greg,

Thanks you for your warm welcome.

I’m facing the problem in both cp and front end .
I checked the channel entries and templates in mysql and seem to have that problem with Greek characters.
I also checked the templates that are stored as hard files (they are .html now?)and saw the same thing.
But the same file before the conversion which is stored in expressionengine/templates/1.x_templates is perfectly ok.

Regards
Steve

Hi Steve,

Do you have complete backups (templates and DB) from before you performed the upgrade?

Cheers

Greg

Yes Greg , I have.

enterweb,

Can I confirm that your 1.6.9 was a standard install? You never had an issue with characters before?

Did you upgrade to 1.6.9 Full version before upgrading to EE2.x?

From a troubleshooting point of view this would be helpful to complete first.

Would you mind rolling back to 1.6.9 please? Then do the upgrade to Full version.
You will find The Full version of 1.6.9 in your 2.x download

I rolled back to 1.6.9.
Tried to make the upgrade again but I got a javascript alert that no errors were found but the installation failed.
After a refresh I’m getting a database error.
I didn’t have that problem the first time I tried to upgrade.
Both times patched the wizard.php as stated here
but this times I think didn’t work. So is it possible to send me the patched files?
I don’t know if I’m gonna face the same problem with the encoding again, but first I have to complete the upgrade.. 😊

enterweb,

EE 2.1 has just been released. Can download the latest version and try your upgrade with that please.

I upgraded with the new 2.1 version but have the same problem with encoding.

enterweb,

What collation is your MySQL database and its tables? Also, what software are you viewing the flat template files in (where the characters appear correctly?)

All tables have utf8_general_ci as collation except: exp_accessories, exp_channel_entries_autosave,    exp_cp_search_index, exp_fieldtypes, exp_layout_publish and exp_snippets who have latin1_swedish_ci.The collation of the db is utf8.

The problem is not only with the flat template files. It’s also with channel entries that contain Greek characters.
It looks the same in the frontend, cp and when I try to open a template file with an editor (bbedit for example). The only flat files that don’t have problem with encoding are the ones in expressionengine/templates/1.x_templates but I guess these are the files before the upgrade.

enterweb,

I am pinging the devs on this one. Hold tight while this happens. Thanks for your patience so far.

Do you’ve got a link to the site where we can see this for ourselves?

Yes the link is :

http://www.enterweb.gr/ee

Did you modify the database in any way prior to the upgrade? What character set were you using, iso-8859-7?