Make WordPress Core

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#4314 closed defect (bug) (fixed)

2.2 XML-RPC Post Reports Incorrect/Malformed Time

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


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.

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 (1)

xmlrpc.php-dif (1.7 KB) - added by josephscott 8 years ago.

Download all attachments as: .zip

Change History (15)

comment:2 @redsweater8 years ago

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.


comment:3 @foolswisdom8 years ago

  • Keywords xml-rpc added
  • 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

comment:4 @foolswisdom8 years ago

  • Owner changed from anonymous to josephthomas

comment:5 @foolswisdom8 years ago

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

comment:6 follow-up: @iacas8 years ago

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.

comment:7 @foolswisdom8 years ago

  • Owner changed from josephthomas to josephscott

comment:8 in reply to: ↑ 6 @foolswisdom8 years ago

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 .

@josephscott8 years ago

comment:9 @josephscott8 years ago

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

comment:10 @rob1n8 years ago

  • Keywords has-patch commit added
  • Owner changed from josephscott to rob1n
  • Status changed from new to assigned

Looks good.

comment:11 @markjaquith8 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

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

comment:12 @markjaquith8 years ago

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

comment:13 @markjaquith8 years ago

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

comment:14 @markjaquith8 years ago

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

Note: See TracTickets for help on using tickets.