This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
May 24, 2011 5:10pm
Subscribe [3]#1 / May 24, 2011 5:10pm
This question may be related to a resolved thread.
When I submit an entry with some non ascii chars in one field, this field results empty.
I’m running EE 2.1.5 on my laptop with Apache/2.0.64 PHP/5.3.5 MySQL 5.5.9.
In my config.php file I have $config[‘charset’] = “UTF-8”; mod_security is not enabled on my apache.
Any suggestions?
Thanks,
Gab
#2 / May 25, 2011 4:07am
Hi Gab,
What type of custom field are you using?
Can you share the characters you have tried so we can try and replicate?
Is it empty on the front-end or after submission the characters have disappeared from the field in the publish form?
#3 / May 25, 2011 4:31am
Hi John, thanks for the reply.
Hi Gab,
What type of custom field are you using?
It is a simple text area
Can you share the characters you have tried so we can try and replicate?
Sure, I tried to insert a dummy string like รจรจรจ, but the problem happens even with a single non ascii char.
Is it empty on the front-end or after submission the characters have disappeared from the field in the publish form?
When I fill the field on the backend and then I sumbit the form I see an error message informing that the text area is a required field (indeed it is required), and the text I entered is disappeared from text area, the other fields are filled with values I entered.
Other informations:
Database encoding is ci_general_utf8
I tried disabling XSS filter but I had no luck.
Gab
#4 / May 25, 2011 5:07pm
This is kinds of a best guess, but what happens if you use utf-8 instead of UTF-8?
#5 / May 25, 2011 5:22pm
This is kinds of a best guess, but what happens if you use utf-8 instead of UTF-8?
Sue, now it works… it sounds to me strange because I did a “straight” installation of 2.1.3 and than I upgraded to the latest beta but I never changed manually this setting. Anyway, I tried to put again UTF-8 uppercase and the system did not accept non ascii chars anymore, so the problem was clearly with encoding case.
Thanks for the support.
Gab
#6 / May 25, 2011 5:25pm
It’s a really funny bug which has been reported and I believed fixed for the next stable release. Glad things are working again. If anything else comes up, please do let us know in a new thread..