Opened 15 years ago
Closed 11 years ago
#11303 closed task (blessed) (maybelater)
XMLRPC (and APP) APIs should expose all Post/Page/Comment management functionality
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.9 |
Component: | XML-RPC | Keywords: | close |
Focuses: | Cc: |
Description
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.
Change History (8)
#1
in reply to:
↑ description
@
15 years ago
#3
@
15 years ago
I guess this would need to be handled in 3.0 in some way, as we now have auto-drafts as well.
#5
@
15 years ago
- Keywords close added
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.
#6
@
15 years ago
- Milestone changed from 3.0 to Future Release
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.
Replying to westi:
For reference, this refers to changeset [12303].