[wp-trac] [WordPress Trac] #15466: Database errors on dashboard

WordPress Trac wp-trac at lists.automattic.com
Tue Sep 4 11:20:09 UTC 2012


#15466: Database errors on dashboard
----------------------------+-----------------------
 Reporter:  Viper007Bond    |       Owner:
     Type:  defect (bug)    |      Status:  reopened
 Priority:  normal          |   Milestone:
Component:  Administration  |     Version:  3.1
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+-----------------------
Changes (by bobbingwide):

 * status:  closed => reopened
 * resolution:  worksforme =>


Comment:

 Not sure if I'm suppposed to open a new defect or reopen this one. I have
 had a similar problem this morning when I views the Dashboard. As with the
 original report this problem is  only occurring on one blog, running
 locally on Windows. I actually get two database errors, one from the
 WordPress blog widget and the other from the Plugins widget. For the
 WordPress blog error the incorrect string value is  '\xE2\x86\x92'. This
 is the right arrow (→) between Dashboard and Updates in post 2383 from
 wordpress.org/news.

 In this particular database the wp_options table is defined with collation
 latin1_swedish_ci, whereas on most other databases the collation is
 utf8_general_ci

 I imported the database to my Windows system from a backup created using
 backupwordpress.
 Possibly relevant lines from the mysql dump file are:
 -- MySQL dump 10.13  Distrib 5.1.63, for pc-linux-gnu (i686)
 -- Server version       5.1.63-cll

 DROP TABLE IF EXISTS `wp_options`;
 /*!40101 SET @saved_cs_client     = @@character_set_client */;
 /*!40101 SET character_set_client = utf8 */;
 CREATE TABLE `wp_options` (
   `option_id` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
   `option_name` varchar(64) NOT NULL DEFAULT '',
   `option_value` longtext NOT NULL,
   `autoload` varchar(20) NOT NULL DEFAULT 'yes',
   PRIMARY KEY (`option_id`),
   UNIQUE KEY `option_name` (`option_name`)
 ) ENGINE=MyISAM AUTO_INCREMENT=9996 DEFAULT CHARSET=latin1;
 /*!40101 SET character_set_client = @saved_cs_client */;

 So I guess it's the latin1 that's causing the problem.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/15466#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list