I have just migrated a Tiki from one server to another and ran into
UTF-8 Problems. The browser showed Umlauts as the dreaded diamonds with
question marks in them.
Both servers are fully utf-8 compliant as described in
http://tikiwiki.org/UTF-8
The big problem is that on the new server PDO is available while it
isn't on the old one. According to the mailing list PDO is not default,
but as far as I can see in the code PDO will be default, if available
and not set otherwise. Setting
$api_tiki='adodb';
in db/local.php fixes the special character problem.
The issue seems to be that PDO gives a silent fuc# about encodings and
just pumps everything to the database and back as you hand it to it.
Additionally PHP/PDO doesn't read your my.cnf and therefore doesn't know
which encoding to use.
A quick fix is telling PDO which encoding to use - line 39 in
db/tiki-db-pdo.php :
$dbTiki = new PDO("$db_tiki:$db_hoststring;dbname=$dbs_tiki",
$user_tiki, $pass_tiki,array(PDO::MYSQL_ATTR_INIT_COMMAND => "SET NAMES
utf8"));
But I think that this is not safe to commit...
e.g. someone started with Tiki on MySQL 4.0 which used latin1 as
default, so all her tables are latin1. She upgrades MySQL to 5.1, but
doesn't change the Tiki database to default to utf-8 and hasn't
converted the database. Then the PDO-fix above will most probably
produce the same problem, just the other way around...
No idea, what to do actually, but wanting to raise awareness here!
This is a dangerous issue as people with utf-8 databases upgrading their
system or Tiki and switching automagically over to PDO will end up with
mixed stuff in their database: clean UTF-8 and double-byte
ansi-control-characters which MySQL converted to their right unicode
codepoints (freaky, hm? ;) ).
I hope, I was capable of describing the problem in a way that's
understandable....
SET NAMES utf-8 is used since r30000. There was a lot of work on UTF-8 since March. The installer should propose to fix upgrade issues.
If you see any problem left in 6.1, feel free to reopen.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
Unable to connect to show.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |