[wp-trac] [WordPress Trac] #24822: XMLRPC wp.editPost doesn't update existing keys

[WordPress Trac]

#24822: XMLRPC wp.editPost doesn't update existing keys
--------------------------+----------------------
 Reporter:  jmaimarc      |       Owner:
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  XML-RPC       |     Version:  3.3
 Severity:  normal        |  Resolution:  invalid
 Keywords:  has-patch     |
--------------------------+----------------------

Comment (by jmaimarc):

 I have to continue to disagree. I don't mean to be obtuse. I want to
 understand.

 The function, as it's written, checks if 'id' is set, or adds a new
 postmeta row. WP allows to check for unique meta keys (c.f.
 add_post_meta() ), but doesn't employ it in this function. (This actually
 refers to ticket #25146, but it's all related).

 That means either the burden of storing the WP postmeta ids is on the
 remote application, or the remote application has to double the work by
 first fetching the post data via wp.getPost, parse out the custom fields,
 set the updated custom field array with id,key & value , and then send the
 wp.editPost back. That will cause response delay, increase bandwidth,
 potential routing errors, hurt kittens, etc. I'm not sure this is the most
 efficient way to do it.

 I'm also not sure what metadata security refers to. You mean data
 tainting?

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24822#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software