[wp-trac] [WordPress Trac] #23495: Special characters can truncate WP Option value

WordPress Trac noreply at wordpress.org
Mon Feb 18 12:41:19 UTC 2013


#23495: Special characters can truncate WP Option value
--------------------------+------------------------------
 Reporter:  TobiasBg      |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  close         |
--------------------------+------------------------------
Changes (by TobiasBg):

 * keywords:   => close


Comment:

 Thanks for testing.

 I've played with this some more, and it seems more of a mySQL thing.
 I can confirm it on several different sites, with the easiest way being
 copying the string
 {{{
 test1𠆢test2
 }}}
 into any text field on /wp-admin/options.php and saving.

 But then I could also reproduce it by adding that string to wp_options
 directly via PHPMyAdmin.
 After checking some of the many settings in the mySQL config that are
 related to character encodings, I found that those are not very
 consistent, and that that's maybe the reason for the issues.

 So, this is not a WP issue, but a mySQL issue. The question is: Is there
 something we can do about or against this? Can we set more mySQL config
 options in regard to UTF8? Can we maybe check if the value that was just
 inserted/updated in the DB matches the value that is read (SELECT)
 immediately after the INSERT/UPDATE?

 Thus, as a bug, this is invalid, but maybe someone has input on this to
 make it an enhancement?

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


More information about the wp-trac mailing list