Delete custom posts via XMLRPC

[nprasath002]

Simple API to support deletion of a single post of any CPT over xmlrpc.

Marking this as a Blessed Task for 3.4 - This is part of the first iteration of XML-RPC new features we will be working on.

There are a number of issues with this current patch:

• Doesn't follow the argument convention of other functions
• Support for multiple deletion is not needed
• You can't tell what did/didn't succeed when an error is returned.

We should have a simple wp.deletePost which mimics wp.deletePage but supports all CPTs (and then we can probably re-work wp.deletePage to call it.

The patch fixed the issues mentioned above

I dont think we need to have blog_id here.
Just id of a post is enough to delete even in a multisite.
Correct if i am wrong

Replying to nprasath002:

I dont think we need to have blog_id here.
Just id of a post is enough to delete even in a multisite.

While technically true, it should still follow the convention that other methods use. In fact, none of the methods actually use the blog_id parameter, but to remove it on some methods and not others is probably not a good idea.

Whitespace issues aside, the new patch looks good.

In [19848]:

XMLRPC: Introduce new create,read,update and delete XMLRPC apis for Posts, Pages and all Custom Post Types.
Introduces: wp.newPost, wp.editPost, wp.deletePost, wp.getPost, and wp.getPosts
See #18429, #18430, #18431, #18432, and #18433 props maxcutler and markoheijnen.

Replying to maxcutler:

While technically true, it should still follow the convention that other methods use. In fact, none of the methods actually use the blog_id parameter, but to remove it on some methods and not others is probably not a good idea.

Yes, please stick to (blog_id, username, password) as first parameters as much as possible. It's already enough of a mess.

Example:

• wp.newPage (username,password,...)
• wp.deletePage (blog_id,username,password,page_id)
• wp.editPage (blog_id,page_id,username,password,...)
• wp.getPage (blog_id,page_id,username,password)

That means instead of clients reusing code to build a common set of parameters, you have to take it case by case.

New bugs or enhancements on new tickets.