jalkut at red-sweater.com
Sat Dec 15 15:57:58 GMT 2007
Hi Joseph - this looks great. Thanks for following up on this. I
guess beggars *can* be choosers because it occurs to me that the main
downside here is that now the API reports more statuses than can be
set in the API. Before it let you set draft/publish, but didn't report
anything, now it reports everything but only lets you set draft/publish.
Would it make sense to support the "post_status" field in incoming
posts, as well?
What I'm mainly concerned by is that now we can get the exact status
of a post, but how do we represent this in a UI to the user? I can
only offer the user a choice between Draft and Publish. So when a
post's status is something else from those two states, how do I know
which state to indicate in the UI? Should I try to guess between which
of Draft and Publish the status is closest to?
Ideally I'd be able to populate a popup menu with all the possible
states for a post, and the user could select from among any of them.
On Dec 5, 2007, at 2:57 PM, Joseph Scott wrote:
> The post_status is now being exposed in metaWeblog.getPost and
> ticket: http://trac.wordpress.org/ticket/4982
> commit: http://trac.wordpress.org/changeset/6358
> I've confirmed that this change is in the 05-Dec-2007 nightly build,
> if you don't want/can't use -trunk from subversion.
> If you have an interest in making use of this data please test it
> out so that we can iron out any potential bugs before 2.4 comes in
> next month.
> Joseph Scott
> wp-xmlrpc mailing list
> wp-xmlrpc at lists.automattic.com
More information about the wp-xmlrpc