Ticket #6612 (closed defect: invalid)

Opened 6 months ago

Last modified 6 months ago

Problems with setting XML-RPC date using metWeblog.newPost()

Reported by: Da_fonz Assigned to: anonymous
Priority: normal Milestone:
Component: XML-RPC Version:
Severity: normal Keywords: has-patch
Cc: josephscott

Description

Had problems setting a date with newPost and came across this which seemed to fix things. Should this be included as a patch or is there something that we're all missing here?

http://www.franzone.com/2007/07/30/wordpress-xml-rpc-patch-for-metweblog-newpost-method/

Attachments

xmlrpc.php.diff (1.5 kB) - added by josephscott on 04/07/08 17:43:32.

Change History

04/07/08 17:43:21 changed by josephscott

  • cc set to josephscott.
  • keywords set to has-patch.
  • milestone set to 2.6.

I'm amazed that we haven't had blog clients complaining about this. I've put together a patch to address metaWeblog.newPost and metaWeblog.editPost. Date/time is a very sensitive issue with the current blog APIs, so I'm requesting additional feedback from the wp-xmlrpc email list as well.

04/07/08 17:43:32 changed by josephscott

  • attachment xmlrpc.php.diff added.

04/14/08 16:32:54 changed by josephscott

  • status changed from new to closed.
  • version deleted.
  • resolution set to invalid.
  • milestone deleted.

It finally dawned on me what is probably happening here. Instead of sending dateCreated as a dateTime.iso8601, he was probably using the string type.

I've heard back from some of the other blog clients and they haven't had a problem using dateCreated, so I'm closing this as invalid. If further details come up that conclude there is indeed a problem we can always re-open this ticket.