[wp-trac] [WordPress Trac] #10483: Change post_name's length from 200 to 400

WordPress Trac wp-trac at lists.automattic.com
Sat Mar 19 10:47:22 UTC 2011

#10483: Change post_name's length from 200 to 400
 Reporter:  elnur         |       Owner:  ryan
     Type:  enhancement   |      Status:  reopened
 Priority:  low           |   Milestone:  Future Release
Component:  Permalinks    |     Version:
 Severity:  minor         |  Resolution:
 Keywords:  dev-feedback  |

Comment (by linuxologos):

 Replying to [comment:13 hakre]:
 > Replying to [comment:12 linuxologos]:
 > > Thanks for giving the opportunity to discuss this.
 > >
 > > This is quite a big problem for languages with an alphabet totally
 different from English. We can't have a post_name with more than ~38
 letters, since '''every''' letter is urlencoded to be stored in the
 database, so every letter is converted into many more characters,
 dramatically cutting down the maximum possible length of the "real" post-
 > It's probably worth to drop the urlencoding then inside the storage
 layer. AFAIK MySQL should be able to store UTF8 in colums, so to have 200
 true UTF8 characters instead of 38 to 200 urlencoded, subset of us-ascii
 > The related refactorings could benefit the overall UTF8 support of the
 application as a bonus.

 MySQL is able to store UTF8 indeed and that is already the fact for
 post_content and post_title in (wp_)posts table. They don't get urlencoded
 before stored in the db. post_name ''is'' urlencoded though, and I'm not
 sure if it's technically safe to alter this.

Ticket URL: <http://core.trac.wordpress.org/ticket/10483#comment:14>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list