Brandon wrote: Actually, before blaming everything else, you may want to verify some things.
You know, I need
your help when I should solve
your issue. Did you verify the collations of your database tables and columns with phpMyAdmin or a similar tool? And if they are indeed different, did you try to solve the issue? Or did you just came back to blame SermonSpeaker?
You know, the default collation for a database is set by the server. To my knowledge Joomla doesn't set a collation, all it does is set the default charset for a table to "utf8". The server then decides which collation will be applied and it takes the default collation for the "utf8" charset to do that. SermonSpeaker does no different.
What I think happened is that your old Joomla 1.5 database had different collations than your Joomla 2.5 database. When you copied the data, the SermonSpeaker tables in your Joomla 2.5 database still had the collation of the Joomla 1.5 database. Now that usually doesn't generate a problem.
But with the update to SermonSpeaker 4.4 a new table was created. This table was created with the default collation of your Joomla 2.5 database and thus is different to the rest of the SermonSpeaker tables.
I think this is the problem you face and the solution is to change the collation of the SermonSpeaker tables (and maybe columns) to what the rest of the database has.
This is by the way not something that can (or has to) be done in an update. It's related to the migration between SermonSpeaker 3.x and 4.x and due to the (stupid) way Joomla handled this migration this is a lot of handwork.
However I'm always willing to help people as long as they ask politely.
