theug

Silly question. Did you actually install Piwik SW on your server?

It may be late, but did you put in address for your Piwik installation with https:// in it? I just found out that you should not do that, as the plug-in sends the tracking to website with https://http//sub.example.com. It is a silly bug, cause of which I have lost couple months worth of stats.

I would s’pose it can be done using actual WP mechanisms. I didn’t get a chance to work on multi-author blog yet, but I, as an administrator, get e-mail notification about any comment (live, or awaiting moderation).

After some search, discussion, and fine handywork with the file, hammer and ductape, I figured this out. Firstly, it was necessary to set the collation to UTF as soon as DB was created. Secondly, it is important to add SET NAMES to the /wp-includes/wp-db.php file. This way DB will properly understand non-latin characters.

I wasn’t able do decode corrupted dump, although I still think it is possible, but I used built-in export/import system, which perfectly exported the XML file in proper encoding. I had some problems with import, when some internal links got lost, so I had to manually edit DB to fix broken relations. But all in all it is fixed now.

I still would argue that SET NAMES directive should be the standard part of UTF-based WP.

I read up on charsets and collations in MySQL docs, and found that latin1_swedish_ci is the default collation for cp1252 West European (which is default charset for MySQL). That is still weird: why doesn’t WP convert DB to UTF-8, if I specified UTF-8 as the default encoding?

Is that because some hosters won’t allow for scripts to change DB settings?

Easily a plug-in. There could be some custom work, or just nicely combined Ultimate Tag Warrior and Post Teaser plug-ins.