Problem when adding a new form + and then to log in

[Nikita007]

Hello,

I tried to add a new form and everything it OK until step 6, but when I clicked on FORM LIST, I get the following error:
---------------
Error:
Failed query in _ft_cache_form_stats, line 1605
Debug:

Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '='
---------------

Then when I log in, I have this error message and don't see the form I've just added.

Could you please help?

Many thanks

PS: I've upgraded to the latest version 2.0.0-beta-20090923 and noticed that there is a bug on the version name. When I click on the button "Check for updates", it says "2.0.0-beta-20090923 is an invalid core version!" - on your file you put 2.0.0-beta-20090823 instead of 2.0.0-beta-20090923!

[Ben]

Hi Nikita,

This is a bug. All database tables should be utf8_general_ci, but I see on my own installation that a few module tables - and more importantly the generated form tables - are latin1_swedish_ci. This can cause that error message you saw (but this is pretty rare, actually - most database configurations won't care). But more importantly, it can cause problems on non-latin based language sites.

PS: I've upgraded to the latest version 2.0.0-beta-20090923 and noticed that there is a bug on the version name. When I click on the button "Check for updates", it says "2.0.0-beta-20090923 is an invalid core version!" - on your file you put 2.0.0-beta-20090823 instead of 2.0.0-beta-20090923!

Ack! I'll release a fix for both of these things today.

However: it WON'T fix your problem for your existing table, since it's already been created. To fix it, you'll need to manually edit the database table collation. To do this in phpMyAdmin, click on the "structure" icon/link for the table, then on "Operations" in the top nav. Then change the collation to utf8_general_ci.

Sorry for the fuss.

- Ben

P.S. I've reported the bug here: http://bugs.formtools.org/index.php?cmd=view&id=146

[Nikita007]

I did it, but I still had the same problem.

Then I saw that "collation" for the new form I added was still "latin1_swedish_ci" and I changed manually the collation of all fields in that table to "utf8_general_ci".

Now I can log in and don't have the error message anymore.

But I noticed that the tables "subs_module_pages, subs_module_swift_mailer_email_template_fields, subs_sessions" are "latin1_swedish_ci". Should I also change them manually to "utf8_general_ci" or can I leave them like it is?

Thanks

[Ben]

Hi Nikita,

Hmm... fair question. It won't hurt to change them, so perhaps you should. For anyone else reading this, as mentioned, this isn't a problem on all systems, just some like Nikita's. I just released an new core build today that fixes it for the core, but not the modules. I'll fix them separately.

Ben

[Nikita007]

Hi Ben,

I changed all tables to "utf8_general_ci".

I tested my form and fill in the form with text with accents and noticed a problem.

For example, if I enter "Anémone" in a field, it only write "An" in the database. It write the letters before the accent and remove all the letters after the accent...

Can you please help?

Many thanks.