XMLRPC (and APP) APIs should expose all Post/Page/Comment management functionality

[westi]

In #11243 we hid the trash status from wp.getPages() we also hide it for pages (and comments I guess).

Really these apis should be fully featured to allow clients to support the new things the api does.

We should revert the change made for trash for 2.9 and promote the fact that clients should be graceful when using these apis so as to cope when we introduce new features.

We also need to review the need for extra apis to allow trashing/untrashing of posts/pages/comments etc.

Replying to westi:

In #11243 we hid the trash status from wp.getPages() we also hide it for pages (and comments I guess).

For reference, this refers to changeset [12303].

westi: are you still interested in this? Or is it to be punted out to 3.1?

I guess this would need to be handled in 3.0 in some way, as we now have auto-drafts as well.

sivel, ryan, josephscott and I had a conversation about this today. Joseph's argument was that apps should first check for a list of all available stati before then calling getPages(). I believe the result of the conversation was that this ticket should be closed.

I'm not convinced we should close this ticket.

I think we need to review in the future how remote publishing clients can access the information about post types / statuses to be able to automatically generate a relevant ui.

Moving to Future.