Ticket #8777 (reopened enhancement)

Opened 3 years ago

Last modified 3 years ago

Provide access to sticky status via XMLRPC and AtomPub

Reported by: redsweater Owned by: josephscott
Priority: normal Milestone: Future Release
Component: AtomPub Version: 2.7
Severity: normal Keywords: needs-patch
Cc: joseph@…

Description (last modified by ryan) (diff)

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

xmlrpc.php.diff Download (1.8 KB) - added by josephscott 3 years ago.
xmlrpc.php.2.diff Download (1.8 KB) - added by josephscott 3 years ago.

Change History

  • Keywords has-patch added
  • Version set to 2.7

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.

It would be also great to expose in AtomPub if a given post status is private.

<wp:private>yes</wp:private>

comment:3   ryan3 years ago

(In [10382]) Provide access to sticky status via XMLRPC. Props josephscott. see #8777

comment:4   ryan3 years ago

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)

comment:5 follow-up: ↓ 6   znarfor3 years ago

Hmm, what about AtomPub ? The changeset only fix XML-RPC part of the issue.

comment:6 in reply to: ↑ 5   josephscott3 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.

Nice. Thanks.

  • Keywords needs-patch added; has-patch removed
  • Type changed from defect (bug) to enhancement
Note: See TracTickets for help on using tickets.