WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 20 months ago

#8777 closed defect (bug) (fixed)

Provide access to sticky status via XMLRPC and AtomPub

Reported by: redsweater Owned by: josephscott
Milestone: 2.8 Priority: normal
Severity: normal Version: 2.7
Component: XML-RPC Keywords: needs-patch
Focuses: Cc:

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)

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

Download all attachments as: .zip

Change History (12)

comment:1 josephscott5 years ago

  • 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.

josephscott5 years ago

comment:2 znarfor5 years ago

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

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

josephscott5 years ago

comment:3 ryan5 years ago

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

comment:4 ryan5 years ago

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

comment:5 follow-up: znarfor5 years ago

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

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

comment:7 znarfor5 years ago

Nice. Thanks.

comment:8 Denis-de-Bernardy5 years ago

  • Keywords needs-patch added; has-patch removed

comment:9 Denis-de-Bernardy5 years ago

  • Type changed from defect (bug) to enhancement

comment:10 nacin20 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.

Note: See TracTickets for help on using tickets.