[wp-trac] [WordPress Trac] #25089: XML-RPC server wrongly conflates post_status "future" with "publish"

[WordPress Trac]

#25089: XML-RPC server wrongly conflates post_status "future" with "publish"
--------------------------+------------------
 Reporter:  kailasa       |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.7
Component:  XML-RPC       |     Version:  3.4
 Severity:  normal        |  Resolution:
 Keywords:  2nd-opinion   |
--------------------------+------------------

Comment (by kailasa):

 " I do have to say that you didn't need to hack core since there is a
 filter to add new methods to the XML-RPC. That also mean overwrite a WP
 method."

 Can you explain to me how to implement this? such that the implementation
 falls into /wp-content/themes/myTheme

 and will not be over written on upgrade? My understanding is that

 our revIgniter code is using this call to WP:

 return callXMLRPC("wp.getPosts", pBlogID, pUser, pPassword)

 we need to do this now:


 return callXMLRPC("wp.getPosts", pBlogID, pUser, pPassword, [add filter
 'no-future' struct here])

 The problem is: the xmlrpc server is issue "publish" as the status for all
 future posts.

 So, if we *can* filter the future posts *before* the serve output routine,
 that would be great.

 How?  I am not a word press expert so we need your guidance.

 Then we don't even had to add the struct filter to our wp.getPosts call.

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