Problems with language specific letters - not in content field

Hi,

I’m struggling with the problem of polish letter automatically changed into "?" signs after Saving the form. What is strange that the page content field is saved properly. I am experiencing problems with fields like "pagetitle", "description" and so on but also with content of the template, content of chunk, ...

Is there a difference in treating the page content field and other fields? I don’t think so, so what can be the problem?

Some tech info:
MODx version 0.9.6.2
Version codename rev 4077
MySQL 5.0.32
All tables and columns has "utf8_general_ci"
$database_connection_charset = ’utf8’;
$database_connection_method = ’SET CHARACTER SET’;
MODx manager configuration set to UTF-8 and language Polish utf-8

Any ideas?

Thx
Greg

I’m not sure this is the only problem for you, but Ver 0.9.6.2 has serious bugs about special characters.
So I recommend to use 0.9.6.3-RC1 in which those bugs are supposed to be fixed.

I’m also having the problem with special characters... but in this way:
I create the document and it outputs all the chars fine, but when I edit the document, all the special chars are scrambled

Quote from: tkfm at Oct 22, 2008, 10:16 PM

So I recommend to use 0.9.6.3-RC1.

Thanks, I’ll try to do that...

Greg

Quote from: tkfm at Oct 22, 2008, 10:16 PM

I’m not sure this is the only problem for you, but Ver 0.9.6.2 has serious bugs about special characters.
So I recommend to use 0.9.6.3-RC1 in which those bugs are supposed to be fixed.

Unfortunately nothing has changed
When I save content it’s fine, but all other fields - titles, long title, names of chunks, descriptions - all special characters in those fields are exchanged to "?"

What can be the problem?

Then I think it must be the collation issue of MySQL database setting.
I’m not an expert of this area, but you can find many trouble reports regarding MySQL collation in this forum.

I hope some MySQL expert will help you.

After upgrading to 0.9.6.3-RC1, check the value of database_connection_charset and make sure it is still ’utf8’. There was a bug in the advanced upgrade option that was causing this field to be blank.

Also, if the problem still persists, try using SET NAMES in the database_connection_method and/or double-check to make sure the actual database charset/collation is utf8/utf8_general_ci, matching the tables and columns...