I recently started to get a ton of 500 errors from spam bots on one of my installations. Live people can comment just fine, but for some reason the automated comments are dying. The error log is filled with lines like this:
[21-Jul-2008 14:07:30] WordPress database error Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation ‘=’ for query SELECT comment_ID FROM wp_xxxxxx_comments WHERE comment_post_ID = ’44’ AND ( comment_author = ‘blahblahblah’ OR comment_author_email = ‘RktzKr2OXo@msn.com’ ) AND comment_content = ‘{spammy comment snipped}’ LIMIT 1 made by wp_allow_comment
The comments table has a default charset of latin1, so not sure why this would be happening. I did find some references to older versions of MySQL having this issue when checking fields holding emails if the table was utf8, since the ‘@’ literal is a different charset than utf8, but since the table in this case is latin1 I’m not sure how that ties in. Unless WP is doing some charset conversions before running queries? In any case not sure why only automated comment postings would trigger this.
(@mvandemar)
15 years, 8 months ago
I recently started to get a ton of 500 errors from spam bots on one of my installations. Live people can comment just fine, but for some reason the automated comments are dying. The error log is filled with lines like this:
[21-Jul-2008 14:07:30] WordPress database error Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation ‘=’ for query SELECT comment_ID FROM wp_xxxxxx_comments WHERE comment_post_ID = ’44’ AND ( comment_author = ‘blahblahblah’ OR comment_author_email = ‘RktzKr2OXo@msn.com’ ) AND comment_content = ‘{spammy comment snipped}’ LIMIT 1 made by wp_allow_comment
The comments table has a default charset of latin1, so not sure why this would be happening. I did find some references to older versions of MySQL having this issue when checking fields holding emails if the table was utf8, since the ‘@’ literal is a different charset than utf8, but since the table in this case is latin1 I’m not sure how that ties in. Unless WP is doing some charset conversions before running queries? In any case not sure why only automated comment postings would trigger this.
Any help would be appreciated, thanks.