Aug 2nd, 2009, 11:26 AM
Hi krko,
That's very strange...! I just checked and you're quite right, some tables don't have the correct collation. Just so you know, you can safely change the collations without messing with any of Form Tools code. I'd set it to utf8_general_ci like the other tables. I'll log this as a bug and address it in the next release.
Things to check:
- Check your /global/config.php file doesn't contain a $g_unicode = false; line and your /global/library.php does contain a $g_unicode = true; line (unicode is enabled by default, so unless you edited it this should be fine).
- When you look at the database directly (e.g. via phpMyAdmin or something), does the newly inputted data (i.e. inputted since you changed the collation type on the field) look correct? Or does it appear as question marks / nonsense chars there as well? If so, it looks like the problem is with the information getting to the database correctly. Either way, it's a big clue.
Also, is your form a POST or an API form?
- Ben
That's very strange...! I just checked and you're quite right, some tables don't have the correct collation. Just so you know, you can safely change the collations without messing with any of Form Tools code. I'd set it to utf8_general_ci like the other tables. I'll log this as a bug and address it in the next release.
Things to check:
- Check your /global/config.php file doesn't contain a $g_unicode = false; line and your /global/library.php does contain a $g_unicode = true; line (unicode is enabled by default, so unless you edited it this should be fine).
- When you look at the database directly (e.g. via phpMyAdmin or something), does the newly inputted data (i.e. inputted since you changed the collation type on the field) look correct? Or does it appear as question marks / nonsense chars there as well? If so, it looks like the problem is with the information getting to the database correctly. Either way, it's a big clue.
Also, is your form a POST or an API form?
- Ben