Ticket #4314 (closed defect: fixed)

Opened 1 year ago

Last modified 9 months ago

2.2 XML-RPC Post Reports Incorrect/Malformed Time

Reported by: iacas Assigned to: rob1n
Priority: high Milestone: 2.2.1
Component: XML-RPC Version: 2.2
Severity: critical Keywords: xml-rpc dateCreated date timezone has-patch commit
Cc:

Description

WordPress 2.2 reports the incorrect time - and perhaps a malformed time - when a desktop application requests the information. This occurs both when posting a single article (a desktop app will then refresh that individual listing) and when refreshing all entries.

This may be related to issue 4158, but I can't be sure. http://trac.wordpress.org/ticket/4158

I've verified this issue on several servers and with a clean install of WordPress 2.2., as well as with at least two (ecto, MarsEdit) desktop app blog editors.

Attachments

xmlrpc.php-dif (1.7 kB) - added by josephscott on 05/22/07 18:45:26.

Change History

05/22/07 15:52:48 changed by iacas

Originally reported (by me) here: http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time

05/22/07 15:54:24 changed by redsweater

This strikes me as a pretty critical issue, since it changes behavior that desktop apps have relied upon for a long time.

May I suggest reverting to 2.1.3 format dates until a more thorough survey of what desktop applications actually expect is conducted? It will at least fix things for my app (MarsEdit) and Ecto, and probably other desktop apps whose users have not yet discovered the bug.

Daniel

05/22/07 16:09:31 changed by foolswisdom

  • keywords changed from dateCreated date timezone to xml-rpc dateCreated date timezone.
  • priority changed from normal to high.
  • severity changed from major to critical.
  • summary changed from 2.2 Reports Incorrect/Malformed Time to 2.2 XML-RPC Post Reports Incorrect/Malformed Time.

05/22/07 16:10:04 changed by foolswisdom

  • owner changed from anonymous to josephthomas.

05/22/07 16:11:44 changed by foolswisdom

iacas, the versions of ecto, MarsEdit may also be relevant. ?

(follow-up: ↓ 8 ) 05/22/07 16:19:05 changed by iacas

I don't believe the versions are relevant. It fails on several versions of MarsEdit and the latest version of ecto. It had been working correctly prior to WordPress 2.2 on both.

I did discover that if the strings "Ymd\TH:i:s" are changed to "Ymd\TH:i:s\Z" in xmlrpc.php, the date is correctly reported and displayed in blog editors. I don't consider that any more than a temporary band-aid.

05/22/07 16:25:20 changed by foolswisdom

  • owner changed from josephthomas to josephscott.

(in reply to: ↑ 6 ) 05/22/07 16:38:48 changed by foolswisdom

Replying to iacas:

I don't believe the versions are relevant.

As I am sure you know, the various components is almost always relevant if someone has to look at a problem months later.

Noting: Latest version of Ecto is 2.3.1 and MarsEdit is 1.1.8 .

05/22/07 18:45:26 changed by josephscott

  • attachment xmlrpc.php-dif added.

05/22/07 18:46:23 changed by josephscott

I've uploaded a patch to add the trailing Z for returning date/time data.

05/22/07 19:29:41 changed by rob1n

  • keywords changed from xml-rpc dateCreated date timezone to xml-rpc dateCreated date timezone has-patch commit.
  • owner changed from josephscott to rob1n.
  • status changed from new to assigned.

Looks good.

05/22/07 19:57:50 changed by markjaquith

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [5513]) explicitly state Zulu time for desktop editors. Props Erik Barzeski and Joseph Scott. fixes #4314 for trunk

05/22/07 19:58:00 changed by markjaquith

(In [5514]) explicitly state Zulu time for desktop editors. Props Erik Barzeski and Joseph Scott. fixes #4314 for trunk

05/22/07 19:59:54 changed by markjaquith

[5514] was for 2.2.x, not trunk (chalk that up to hyper-up-return-itis).

08/17/07 03:18:58 changed by markjaquith

(In [5888]) Send dateCreated as local blog time, add date_created_gmt with GMT value. Props josephscott. fixes #4624. refs #4158, #4314