Ticket #8777 (reopened enhancement)
Provide access to sticky status via XMLRPC and AtomPub
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | AtomPub | Version: | 2.7 |
| Severity: | normal | Keywords: | needs-patch |
| Cc: | joseph@… |
Attachments
Change History
comment:1
josephscott — 3 years ago
- Keywords has-patch added
- Version set to 2.7
It would be also great to expose in AtomPub if a given post status is private.
<wp:private>yes</wp:private>
- Status changed from new to closed
- Resolution set to fixed
- Description modified (diff)
Hmm, what about AtomPub ? The changeset only fix XML-RPC part of the issue.
comment:6
in reply to:
↑ 5
josephscott — 3 years ago
- Cc joseph@… added
- Resolution fixed deleted
- Status changed from closed to reopened
- Component changed from General to AtomPub
- Milestone changed from 2.8 to Future Release
Replying to znarfor:
Hmm, what about AtomPub ? The changeset only fix XML-RPC part of the issue.
Making this happen in AtomPub will have to be part of a larger effort. We'll have to bite the bullet and add our own custom namespace for WordPress specific AtomPub fields since there's no standard way to indicate 'sticky'.
I've re-opened this ticket and marked as 'Future Release'. When we a WordPress namespace then we can take care of this.
Note: See
TracTickets for help on using
tickets.


Here's a patch that adds a boolean 'is_sticky' field to metaWeblog.getPost/editPost/newPost XML-RPC methods. I'll ping the AtomPub email list and see what's considered the right way to expose this functionality via AtomPub.