[wp-trac] Re: [WordPress Trac] #6784: options with content in strange languages do not deserialize properly

[WordPress Trac]

#6784: options with content in strange languages do not deserialize properly
-----------------------------------------------------+----------------------
 Reporter:  Olav Kolbu                               |        Owner:  anonymous
     Type:  defect                                   |       Status:  new      
 Priority:  normal                                   |    Milestone:  2.5.1    
Component:  General                                  |      Version:  2.5      
 Severity:  normal                                   |   Resolution:           
 Keywords:  deserialize, get_option, character sets  |  
-----------------------------------------------------+----------------------
Comment (by Olav Kolbu):

 Hi!
 Your suspicions were right. My collation on wp_options is
 latin1_swedish_ci. DB_CHARSET is 'utf8', DB_COLLATE is ''.
 Read up on charsets in WP and presumably I'm a victim of the pre-2.2
 defaults. I've converted
 my tables to utf8_general_ci now (using a plugin), and my test no longer
 fails. My Google News plugin now appears to handle cyrillic, arabic and
 other languages fine as well. Thank you for your time and feel free to
 close this bug as solved. You might want to add an admin-warning somewhere
 if the mysql table types do not match the selected charset for the blog
 though? Perhaps in the upgrade-script.

 Oh yeah, if you're bored there should be a system for clearing out old
 cached MagpieRSS feeds. As it is now they're just accumulating in
 wp_options, and at several hundred kb a pop that can quickly grow a
 database. Would have supplied the code for this, but I suspect you're
 planning on ditching MagpieRSS anyway. :-)

-- 
Ticket URL: <http://trac.wordpress.org/ticket/6784#comment:3>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software