(mysql_fetch bug in few version of 4.4)
Can you explain this more detailed?
--> I've written some of the charset code for the mysql(I) drivers for mdb2, and I don't think we have special PHP4 bugreports regarding charsets.
Of course, if you store data with an application like phpMyAdmin (which handle charsets correct) in the db, and then retrieve the data with a wrong client encoding in PHP, the result is not correct.
--> same happens with cmsms at the moment.
Again, for general installations "set names" (if you want uncomment query in include.php) implies that you must have mysql 4.1 to work well, but until a month ago I had two sites MLE with mysql 3.23.58!!
That's also no problem, because mysql in your (x)html output.
- No access to mysql/apache resources: php query:
SET NAMES utf8 or SET CHARACTER_SET utf8
What does you mean with "no access"?
BTW:
"SET CHARACTER SET" is in most times not what you want. This sets the connection charset to the default server charset. "SET NAMES" (or better mysql(i)_set_charset) is the correct way.
- database/table/columns text: UTF8
- header('Content-Type: text/html; charset=utf-8' );
-
That's what I also have. But as I've written above:
For the DB this makes only sense, if you use "SET NAMES 'utf8'" and also correct the wrong chars in the db and adjust one index.
If you don't use "SET NAMES", better use "latin1" in the db (and save space).
That works without problems for the base cmsms. If you install additional modules, you can have a problem if only your tables have a default charset utf8, but the db not.