Hello,

I already had xmlsitemap running on a different installation with no problems whatsoever (and I love the module!) so this is probably something I am doing wrong.

I did a fresh install of 6.x1.0-beta 3 (on a totally different site) and I keep getting this error

user warning: Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=' query: SELECT COUNT(xsm.loc) FROM xmlsitemap xsm INNER JOIN system s ON s.name = xsm.module WHERE s.type = 'module' AND s.status = 1 AND xsm.changefreq <> 0 AND xsm.changed <> 0 AND (xsm.priority >= 0 AND xsm.priority <= 1) in /home/hey/public_html/sites/all/modules/xmlsitemap/xmlsitemap/xmlsitemap.module on line 301.

Both sites are running drupal 6.12.

Any ideas?

thank you

Comments

dave reid’s picture

Sounds like your webhost upgrade from a previous version of MySQL or you manually changed your table collation from the default utf8_general_ci.

See these following pages on the same problem/how to switch your database table collation:
http://drupal.org/node/60409
http://drupal.org/node/140303
http://drupal.org/node/303363
http://drupal.org/node/298820
http://mostrey.be/drupal_character_encoding_mysql

avpaderno’s picture

I confirm what already said. The default collation should be utf8_general_ci, and that is the collation Drupal is thought to work with.

zero000x’s picture

wow - that was a quick response - Thank you for the links! I'll check them out.

zero000x’s picture

ok - thank you guys so much. I ran the php file from the following link (which i found listed on one of the pages linked by Dave Reid).

http://bogdan.org.ua/2008/02/08/convert-mysql-database-from-one-encoding...

I copied the SQL Query info it produced, used a find and replace to replace "NOT NULL DEFAULT NULL" with "NOT NULL" and ran it through phpmyadmin - worked like a charm - no errors.

Thanks again!

dave reid’s picture

Status: Active » Fixed

Glad that it worked for you zero000x. Marking as fixed then!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.