[wp-trac] [WordPress Trac] #25089: XML-RPC server wrongly conflates post_status "future" with "publish"
WordPress Trac
noreply at wordpress.org
Thu Sep 11 14:56:31 UTC 2014
#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:
--------------------------------------+---------------------------
Changes (by nacin):
* status: assigned => closed
* resolution: => invalid
* milestone: Awaiting Review =>
Comment:
> If a post has a time in the future, wp_insert_post() automatically
converts 'publish' to 'future' and schedules it. So I'm not actually sure
if this affects XML-RPC interaction at all, and is just designed to smooth
things out for the underlying API and for clients.
I said this 13 months ago. I just confirmed again this is how it works.
XML-RPC converts future to publish, then wp_insert_post() converts it back
if the date is in the future. There is no bug here. There is no unexpected
behavior here.
I've never even used 'future' as a value for wp_insert_post(). It isn't
necessary and it isn't meant to be used directly. It's an internal only
status that is overridden anyway. 'publish' should be used.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/25089#comment:16>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list