need help with UTF-8 migration

[zsero]

I have finally finished my long time upgrading process of 0.11.2 -> 1.2.5 -> and finally 1.4.1, but I still cannot let it work in the default UTF-8 mode, because all the special characters go crazy.

At the moment, I am using the following settings which works, but I would really like to use UTF-8 in the future.

Code: Select all

$config['default_encoding'] = 'windows-1250';
$config['admin_encoding'] = 'windows-1250';

<meta http-equiv="Content-Type" content="text/html; charset=windows-1250" >

TinyMCE editor encoding set to numeric encoding 

It works, except for the menu characters, but I have to insert special characters into the menu manually.

I tried everything, but I don't understand why is my site different from the 1.4.1 default site, which works perfectly with all UTF-8 stuff.

I don't even understand why Edit template page sometimes has an option for selecting encoding, sometimes not. I did something and now it doesn't have the option to choose, but I had it before.

[Pierre M.]

Hello,

'windows-1250';

I tried everything,

Do you have tried a unix hosting ?

Pierre M.

[zsero]

I am on a Debian host.
My problem is the following:

UTF-8 works on a brand new clean CMSMS installation.
UTF-8 doesn't work on my upgraded installation, on the same host.

I tried everything but I don't know how could I get the same settings as a fresh new CMSMS installation.

[alby]

I am on a Debian host.
My problem is the following:

UTF-8 works on a brand new clean CMSMS installation.
UTF-8 doesn't work on my upgraded installation, on the same host.

I tried everything but I don't know how could I get the same settings as a fresh new CMSMS installation.

Depend on many factors.
In new installation, admin part, work always (if you don't touch admin encoding in config.php and if you use utf8 in your DB) in UTF-8
for that very very old release is a problem.
If you have a few pages you can check any pages and replace bad characters (but check first if you have DB/table/varchar UTF8 encoding), with many pages is possible translate many characters with a script (but you must always check)
My advice is, if possible, got to utf8

Alby

[zsero]

My problem is not with the old data in the database, for that I could use a search and replace on the mysql dump.

My problem is that if I create a new page, and I try to enter ő Ő ű Ű in the editor when I save it it goes to ? ? ? ?

On the fresh new installation I could enter any character in the editor, it stays there.

but check first if you have DB/table/varchar UTF8 encoding

What do you mean by that? On the clean new CMSMS installation it has latin1_swedish_ci encoding on content_props table if I click alter table. Where else could I set to UTF-8, except config.php and metadata?