Ticket #7446 (closed enhancement: fixed)
XMLRPC Comments API
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | 2.7 |
| Component: | XML-RPC | Version: | |
| Severity: | normal | Keywords: | comments xmlrpc blessed |
| Cc: | josephscott, redsweater |
Description
Add API to XMLPRC for retrieving and managing comments.
Attachments
Change History
comment:2
josephscott — 4 years ago
- Cc josephscott added
- Type changed from defect to enhancement
- Component changed from General to XML-RPC
There's been some discussion about this on the wp-xmlrpc list: http://comox.textdrive.com/pipermail/wp-xmlrpc/
-
attachment
7446.2.diff
added
Drop separate method for setting comment status. Flesh out editComment.
-
attachment
7446.3.diff
added
Add get_comments(). Register methods. Deprecate some old stuff.
-
attachment
7446.4.diff
added
All methods tested except newComment. It needs some more work.
getComments() accepts optional status and post_id. A separate getPostComments() has been suggested. It'd probably just be an alias to getComments() with different argument passing if we added it.
newComment() needs a little more work. All other methods have had basic testing and are hopefully complete.
In 7446.6 all methods are completed and tested. I left support for unregistered commenting out of newComments for now.
wp-xmlrpc list conversation:
http://comox.textdrive.com/pipermail/wp-xmlrpc/2008-August/000258.html
comment:8
MtDewVirus — 3 years ago
When editing a comment in moderation, http://trac.wordpress.org/browser/trunk/wp-includes/comment.php?rev=8543#L863 is causing the comment to be be approved with any changes to the Approval Status.
- Status changed from new to closed
- Resolution set to fixed
