[wp-trac] [WordPress Trac] #17935: Quick edit in admin bypasses custom_column filters in wp-admin/edit.php

[WordPress Trac]

#17935: Quick edit in admin bypasses custom_column filters in wp-admin/edit.php
----------------------------+-----------------------------
 Reporter:  postpostmodern  |       Owner:  wonderboymusic
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Query           |     Version:  3.2
 Severity:  normal          |  Resolution:  wontfix
 Keywords:  has-patch       |
----------------------------+-----------------------------

Comment (by postpostmodern):

 Replying to [comment:9 markjaquith]:
 > WONTFIX, because this assumption is not true:
 >
 > > Wordpress provides APIs to select extra data along with my post
 >
 > It provides APIs to select extra data when querying multiple posts. But
 code should consider that sometimes posts are selected individually from
 the cache, and provide an appropriate "else" case that fetches any missing
 data.

 I don't understand the assertion that one table, in one place in the
 admin, should be populated by two different methods, depending on whether
 it is done from a normal page load, or by an ajax call - especially if
 there is a solution that can consolidate this logic and not require an
 'else' clause.

 Could you explain the benefit of having two sets of code populate this
 table?  If so, is there a third or fourth way of populating this table
 that I should be aware of?

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