Comments on: WordPress XML-RPC Patch For metWeblog newPost() Method

By: Joseph Scott

Joseph Scott — Mon, 29 Sep 2008 23:49:19 +0000

@Damiano -

Please go back and read my comment. The dateCreated and date_created_gmt values are NOT STRINGS. Their type is dateTime.iso8601. This is not a bug in WordPress.

By: bug: wordpress xmlrpc createDate « dam’s blog

bug: wordpress xmlrpc createDate « dam’s blog — Sun, 28 Sep 2008 16:32:28 +0000

[...] cosa “divertente” Ã¨ che questo bug era gia stato scoperto da Jonathan http://www.franzone.com/2007/07/30/wordpress-xml-rpc-patch-for-metweblog-newpost-method/ piu di un anno fa. Aveva pure fatto una patch. Quello che invece noto Ã¨ che il codice di [...]

By: Damiano Venturin

Damiano Venturin — Sun, 28 Sep 2008 14:49:07 +0000

Hi Jonathan
I’m running in this problem too.
I have just downloaded WP 2.6.2 but I can see a similiar error over there:

the code:
if ( !empty( $content_struct['date_created_gmt'] ) )
$dateCreated = str_replace( ‘Z’, ”, $content_struct['date_created_gmt']->getIso() ) . ‘Z’; // We know this is supposed to be GMT, so we’re going to slap that Z on there by force
elseif ( !empty( $content_struct['dateCreated']) )
$dateCreated = $content_struct['dateCreated']->getIso();

$content_struct['date_created_gmt'] and $content_struct['dateCreated'] are not objects, just strings!

for me the main problem is that I’m running WP directly on wordpress.com so I can’t fix it.

how comes that after a year the code was rewritten but the bug is still there???

By: Jonathan Franzone

Jonathan Franzone — Mon, 14 Apr 2008 20:35:03 +0000

You know you are absolutely correct. The method I was using was pre-formatting the date/time and passing it through as a string. All I had to do was pass it an actual Date object and the XML-RPC (Redstone) library converted it to a dateTime.iso8601 properly.

Thanks for catching that!

By: Joseph Scott

Joseph Scott — Mon, 14 Apr 2008 16:35:38 +0000

I should have asked about this sooner. What I suspect has happened is that you sent the date as a string type instead of using dateTime.iso8601. I’ve heard back from some of the blog clients and they haven’t had any problems using dateCreated. Can you confirm if this is the case?

For now I’m closing the ticket (http://trac.wordpress.org/ticket/6612) as invalid. If something else comes up indicating there is a problem we can always re-open it.

By: Jonathan Franzone

Jonathan Franzone — Mon, 07 Apr 2008 18:14:26 +0000

Cool. Thanks a lot!

By: Joseph Scott

Joseph Scott — Mon, 07 Apr 2008 17:46:25 +0000

I’ve submitted a patch for this as part of ticket 6612 ( http://trac.wordpress.org/ticket/6612 ).

By: ladynada

ladynada — Tue, 07 Aug 2007 07:18:58 +0000

Hi,
I just posted some of my code in this blog message.

http://heartdaughter.com/blogs/elijah/index.php/2007/08/07/390/

regards,
nada

By: ladynada

ladynada — Tue, 07 Aug 2007 03:47:38 +0000

Hi,
I used the four different formats that are in the wp tables. I did not alter them before sending them.

One thing, does not the receiving wp site need to have this fix in the xmlrpc.php?

thank you for the format, I will try that next time!

nada

By: Jonathan Franzone

Jonathan Franzone — Tue, 07 Aug 2007 03:07:58 +0000

I noticed that I get that date whenever the parsing fails. I think the system just populates that as the default, which is probably just the earliest date that the system can use. What format is your date string in?

I’m currently passing dates in the format of “20070715T18:34:00″ and those work fine.