mediawiki

kashani · Posted: Tue Jun 13, 2006 6:21 am Post subject:

That is usually an issue with Mysql not having the charset mediawiki expects. I *think* the fix is to unmask mediawiki 1.6.6 and install it rather than the older 1.4.15 Gentoo currently has a stable. 1.6.6 defaults to utf8 charset rather than latin1 in 1.4.x. Mysql is now defaulting to utf8 which is where the issues come in.

I'm in the middle of this sort of issue myself and didn't have a chance to test things out. You may want to investigate a bit before taking this as gospel.

kashani
_________________
Will personally fix your server in exchange for motorcycle related shop tools in good shape.

Dlareh · Advocate Joined: 06 Aug 2005 Posts: 2102

1.6 is far better anyway

many annoying issues fixed and useful functionality added
_________________
"Mr Thomas Edison has been up on the two previous nights discovering 'a bug' in his phonograph." --Pall Mall Gazette (1889)
Are we THERE yet?

thechris · Veteran Joined: 12 Oct 2003 Posts: 1203

ok, i asked on IRC. it seems there is a file in maintainece/tables.sql with a line involving a varchar(86) or varchar(255) (ending index or something) that should be changed to varchar(7

.
_________________
HW problems. It's a VIA thing.

at240 · l33t Joined: 12 Aug 2005 Posts: 603 Location: UK

thechris · Veteran Joined: 12 Oct 2003 Posts: 1203

[/code]CREATE TABLE /*$wgDBprefix*/categorylinks (
cl_from int(

unsigned NOT NULL default '0',
cl_to varchar(255) binary NOT NULL default '',
cl_sortkey varchar(255) binary NOT NULL default '',
cl_timestamp timestamp NOT NULL,
UNIQUE KEY cl_from(cl_from,cl_to),
KEY cl_sortkey(cl_to,cl_sortkey(128)),
KEY cl_timestamp(cl_to,cl_timestamp)
);
[/code]

the sortkey varchar(255) line is what i changed. i think. sadly i did an emerge -e world and now my changes are undone! i did a mysqldump and found what i set:

ova · Posted: Thu Jul 06, 2006 6:39 pm Post subject:

I found that cleanest solution is to use latin1 encoding for mysql. See this bug report:

http://bugzilla.wikimedia.org/show_bug.cgi?id=1322

There is still unanswered question: Does this mysql table changes are dangerous or not :?:

Thus I just changed mysqld default encoding to latin1 and then used "Backwards-compatible UTF-8" database.

HTH.

kashani · Posted: Thu Jul 06, 2006 7:27 pm Post subject:

I'd say the cleaner solution is to keyword mediawiki and install 1.6 or better and skip the whole utf8/latin1 issue from the start. Unless you really want to migrate your database to utf8 in the next two or three months. It's not terriably painful, but it's an hour or two of work I'd rather not have done.

kashani
_________________
Will personally fix your server in exchange for motorcycle related shop tools in good shape.

ova · Posted: Thu Jul 06, 2006 9:10 pm Post subject:

kashani · Posted: Thu Jul 06, 2006 9:16 pm Post subject:

Really? Were you starting from scratch with no database? IIRC I tested 1.6.7 which worked fine with a default build of Mysql 5.0.22 and then later replaced the db with the one from my 1.4.15 install after doing all the utf8 fixes.

kashani
_________________
Will personally fix your server in exchange for motorcycle related shop tools in good shape.

at240 · l33t Joined: 12 Aug 2005 Posts: 603 Location: UK