Xml-Rpc dateTime inaccurate

[whilo]

As stated in the Xml-Rpc standard the datetime object should be <dateTime.iso8601>. Wordpress seems to only accept <datetime.iso8601> . Otherwise I get a date in 1999 or another user even 1970 (good old Unix).

[foolswisdom]

Same questions as in #3994. Thank you!

[westi]

We only accept ​dateTime.iso8601 as XML is case sensitive. Which is correct according to the spec: ​http://www.xmlrpc.com/spec

[whilo]

​ISO_8601

O.k. I think, I've found the real problem with dateTime objects:
As it is stated here, the format can be both YYYYMMDD and YYYY-MM-DD, but Wordpress ​only supports YYYYMMDD. My application uses the second format, which puts a date of 1999 in the database.

Cheers,
Christian

[rob1n]

I think I can fix this.

[rob1n]

removes dashes

[rob1n]

whilo: does my patch fix the problem for you?

[westi]

I have closed #1528 as a duplicate of this as it is the same issue effectively

[rob1n]

In my second patch, it's all UTC, and uses strtotime() instead for a more extensible approach.

[westi]

Replying to rob1n:

In my second patch, it's all UTC, and uses strtotime() instead for a more extensible approach.

I'm not convinced this is the correct approach as we now lose the timezone offset info provided in the iso8601 formatted string.

I think I prefer the first option or reuse the preg_match in iso8601_to_datetime in wp-includes/formatting.php

[rob1n]

Bump to 2.3.

[josephscott]

We've had a few upheavals with datetime fields in XML-RPC lately. With -trunk right now I think things have been resolved. Do either of the above patches really fix any currently broken items?