[wp-trac] [WordPress Trac] #25089: XML-RPC server wrongly conflates post_status "future" with "publish"

[WordPress Trac]

#25089: XML-RPC server wrongly conflates post_status "future" with "publish"
--------------------------------------+---------------------------
 Reporter:  kailasa                   |       Owner:  markoheijnen
     Type:  defect (bug)              |      Status:  closed
 Priority:  normal                    |   Milestone:
Component:  XML-RPC                   |     Version:  3.4
 Severity:  normal                    |  Resolution:  invalid
 Keywords:  2nd-opinion dev-feedback  |     Focuses:
--------------------------------------+---------------------------

Comment (by rmccue):

 Just to drop a note: the REST API uses `filter[post_status]=future` (since
 it's just WP Query under the hood), but also reports the `status` field
 value as publish. A normal query to get all posts only returns actually
 published posts, regardless of authentication. (The reason we still have
 the filter as future is because a) it's WP Query's way of referring to it,
 and b) we don't support date queries.)

 kailasa, I think the point nacin was making is that the `future` post
 status is just an internal flag to say "the post status is `publish`, but
 not until `post_date`". I'd agree that if you get the most recent posts,
 it shouldn't include future-published posts, but it may break backwards
 compatibility to change this on the XML-RPC endpoints now.

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