[wp-trac] [WordPress Trac] #38693: REST API: Audit `orderby` params and add any others

WordPress Trac noreply at wordpress.org
Tue Nov 29 14:45:47 UTC 2016


#38693: REST API: Audit `orderby` params and add any others
--------------------------+------------------------------
 Reporter:  jnylen0       |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  REST API      |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+------------------------------
Changes (by jnylen0):

 * keywords:   => needs-patch
 * type:  enhancement => defect (bug)


Comment:

 The collection params filters support this use case really nicely - thanks
 for the example.

 `meta_value_num` [https://core.trac.wordpress.org/browser/trunk/src/wp-
 includes/class-wp-query.php?rev=39300&marks=690-691#L675 requires
 `meta_key` to be set in the query] so we shouldn't add that one.

 I can't think of any reason ''not'' to add all of the other parameters
 mentioned above ('none', 'modified', 'parent', 'rand').

 Setting this back to "bug" as it's a regression from previously
 established behavior.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38693#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list