WordPress.org

Make WordPress Core

Opened 8 years ago

Closed 4 years 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 7 years ago.
xmlrpc.php.2.diff (1.8 KB) - added by josephscott 7 years ago.

Download all attachments as: .zip

Change History (12)

#1 @josephscott
7 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.

#2 @znarfor
7 years ago

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

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

#3 @ryan
7 years ago

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

#4 @ryan
7 years ago

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

#5 follow-up: @znarfor
7 years ago

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

#6 in reply to: ↑ 5 @josephscott
7 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.

#7 @znarfor
7 years ago

Nice. Thanks.

#8 @Denis-de-Bernardy
7 years ago

  • Keywords needs-patch added; has-patch removed

#9 @Denis-de-Bernardy
7 years ago

  • Type changed from defect (bug) to enhancement

#10 @nacin
4 years 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.