Opened 4 years ago
Closed 9 months ago
#8777 closed defect (bug) (fixed)
Provide access to sticky status via XMLRPC and AtomPub
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 2.8 |
| Component: | XML-RPC | Version: | 2.7 |
| Severity: | normal | Keywords: | needs-patch |
| Cc: | joseph@… |
Description (last modified by ryan)
The "sticky" status of a post should be accessible by remote clients who use the AtomPub or XMLRPC interface to manage WordPress blogs.
Clients should be able to read and set the boolean value.
Thanks!
Daniel
Attachments (2)
Change History (12)
comment:1
josephscott — 4 years ago
- Keywords has-patch added
- Version set to 2.7
josephscott — 4 years ago
It would be also great to expose in AtomPub if a given post status is private.
<wp:private>yes</wp:private>
josephscott — 4 years ago
- Description modified (diff)
- Resolution set to fixed
- Status changed from new to closed
Hmm, what about AtomPub ? The changeset only fix XML-RPC part of the issue.
comment:6
in reply to:
↑ 5
josephscott — 4 years ago
- Cc joseph@… added
- Component changed from General to AtomPub
- Milestone changed from 2.8 to Future Release
- Resolution fixed deleted
- Status changed from closed to reopened
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.
- Keywords needs-patch added; has-patch removed
- Type changed from defect (bug) to enhancement
comment:10
nacin — 9 months ago
- Component changed from AtomPub to XML-RPC
- Milestone changed from Future Release to 2.8
- Resolution set to fixed
- Status changed from reopened to closed
- Type changed from enhancement to defect (bug)
Given the lack of traction with AtomPub, closing this as fixed for XML-RPC.

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.