[wp-xmlrpc] Problems with dateCreated in metaWeblog.newPost/editPost

[Toby Simmons]

Just to confirm, Zempt has no problems specifying a date in a new post with
payload of with 2.5 off the shelf

<member>
<name>dateCreated</name>
<value><dateTime.iso8601>20080412T07:00:00Z</dateTime.iso8601></value>
</member>



___________________________________
W. Tobias Simmons
Simmons Consulting, Web Design and Marketing
toby at simmonsconsulting.com
http://www.simmonsconsulting.com
Phone: 501.821.4230 / Fax: 501.244.4416
-----Original Message-----
From: Joseph Scott [mailto:joseph at randomnetworks.com] 
Sent: Sunday, April 13, 2008 2:03 AM
To: wp-xmlrpc at lists.automattic.com
Subject: Re: [wp-xmlrpc] Problems with dateCreated in
metaWeblog.newPost/editPost


On Apr 13, 2008, at 12:33 AM, Daniel Jalkut wrote:

> Joseph, I think your instinct to be skeptical because of the lack  
> of complaints among blog clients, is correct.
>
> Have you confirmed the problem? I just tested with MarsEdit and  
> setting a date on a new post seems fine, with a cargo like:
>
> 			<member>
> 			<name>dateCreated</name>
>
<value><dateTime.iso8601>20080414T06:27:14Z</dateTime.iso8601></ 
> value>
> 			</member>
>
> There may be something nuanced that is wrong with the API, but it's  
> not affecting me. I suspect it's not affecting other clients,  
> either.  I haven't looked closely at the fix that the bug reporter  
> is proposing. As long as it doesn't break the current working  
> behavior I'm not opposed to it.


Thanks Daniel.  I suspect what was happening is that they were  
sending the date as a string instead of dateTime.iso8601.  I'm not  
sure why I didn't think about that earlier.

I'll follow up with the ticket on Monday.

--
Joseph Scott
joseph at randomnetworks.com
http://joseph.randomnetworks.com/