You are here

The server was really screaming yesterday. I was trying to understand why.
I thought it was the aggregator module. I did some profiling for the aggregator SQL queries and while I'm at it, I did the same for some other modules and here we go: Here, here, here and here.
I'll be applying them too to the drupal sites I'm hosting whether they like it or not!

ChangeLog:
* Don't try to convert the encoding if the requested one is utf8. return false if the text is not valid utf8 after we convert it.
* Reset the gui when we close the document from the document label close button.

Here's the tarball, md5sum and a gpg-signed md5sum file.
ChangeLog:
Can now open remote files using an external command.
Added an option to insert files.
Some small code improvements and cleanups.
Depend on gtkmm 2.6.0 instead of 2.6.5

Drupal 4.7 sets the database connection to utf8 if you are running MySQL 4.1+
When you upgrade drupal from 4.6 to 4.7 and you are using MySQL 4.1+, drupal will convert the tables to utf8. But it won't if you are running MySQL 4.0.
Your host upgrades MySQL from 4.0 to 4.1+ and drupal will start setting the connection to utf8 BUT MySQL "knows" that the tables are in latin1 encoding. He doesnt know that the data is really utf8 but the tables are latin1. It'll convert the data from latin1 to utf8 and send it to drupal. You'll end up with a broken website due to the double utf8 conversion.