Ticket #4982 (closed defect (bug): fixed)
XMLRPC should expose draft status of entries
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 2.5 |
| Component: | XML-RPC | Version: | 2.3 |
| Severity: | normal | Keywords: | has-patch |
| Cc: | redsweater, josephscott |
Description
Although getRecentPosts returns items whose publish status is "draft," there is no indication in the XML attributes of the status of the item. This leaves remote clients in a tricky position when it comes to relating the status of the post to the user.
I propose a new boolean attribute "wp_draft" be added to these posts, to definitely convey whether the post is a draft or not.
Attachments
Change History
comment:3
josephscott — 4 years ago
Would it be helpful to know the other possible states? Ryan mentioned 5: http://boren.nu/archives/2007/09/05/post-status-transitions/
- publish
- draft
- private
- future
- pending
See also:
http://trac.wordpress.org/browser/trunk/wp-admin/includes/schema.php?rev=6075#L103
Not all of those are applicable to posts though.
Most of those are legacy. Only inherit is still used among those in the schema but not in my list, and it really isn't a public status.
comment:7
josephscott — 4 years ago
In -trunk I see the following potential post status values for a post:
- draft
- private
- pending
- publish
- future
For pages there are the following potential values:
- draft
- private
- publish
There were all the possible states I was able to put posts and pages in using the regular web admin. Does this seem like a reasonable list?
comment:8
josephscott — 4 years ago
The diff adds the 'post_status' field to data returned from metaWeblog.getPost and metaWeblog.getRecentPosts. Just as a note, wp.getPage already provides this for pages in the 'page_status' field.
comment:10
westi — 4 years ago
- Owner changed from anonymous to westi
- Status changed from new to assigned
comment:11
westi — 4 years ago
- Status changed from assigned to closed
- Resolution set to fixed

