[wp-trac] [WordPress Trac] #11083: wp_posts.post_name gets too long to save in DB, after repeated updates

[WordPress Trac]

#11083: wp_posts.post_name gets too long to save in DB, after repeated updates
----------------------------+-----------------------------------------------
 Reporter:  knutsp          |       Owner:                 
     Type:  defect (bug)    |      Status:  new            
 Priority:  normal          |   Milestone:  2.9            
Component:  Administration  |     Version:  2.8.5          
 Severity:  normal          |    Keywords:  post_name, save
----------------------------+-----------------------------------------------
 When the post_name is generated the post_name field is an url encoded
 evrsion om the same string, with some exceptions (like a space translates
 to a dash). So far so good.

 But for every save of a post this string is increased in length with more
 and more such %nn substrings. Example: hello-%73%23%54%10

 In the end the field gets too long to save in the database, and the save
 fails.

 Also: When the default permalink structure is used this behaviour cannot
 be seen or crrected in the edit post page, but may bee seen and corrected
 when using Quik Edit, if one is aware of this bug.

 Some of the users I serve have some private posts for internal use, which
 they update up to one hundred times over a period . They complain that
 ther changes no longer gets saved. And their titles often consists of
 Scandinavian characters (ÆØÅ) and slashes.

 1. The post_name must not grow in length for each update

 2. When the post_name is too long for the DB to handel, it should be
 truncated to avoid DB errors.

 3. When a DB error occurs the users should be warned that the post, or any
 object for that matter, for some reason, was NOT saved. This does not
 happen in this case, at least.

 (This my first bug report to this community)

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11083>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software