Future posts published with Windows Live Writer are scheduled for incorrect time.

[markjaquith]

WP GMT Offset: -05

1. Compose post in Windows Live Writer
2. Set publish time to 1 hour in the future
3. Publish
4. View "Manage > Posts" and verify that publish time is correct (it is).
5. View "Dashboard" and note that pseudo cron has the post scheduled to "fire" in 6 hours.

Tried with a few other times, and it seems to be [Publish Time] - [GMT Offset].

Tried on WordPress.com and the post failed to publish (can't see the scheduled time on the dashboard).

I couldn't trigger this bug with MarsEdit (which uses a different API). I'm leaning towards this being a WLW bug, but it's strange that the publish time would be right but the cron time wouldn't.

This is also another reason why our pseudo cron implementation needs a re-work... you shouldn't be able to schedule a post to publish at any time other than its publish date!

[lloydbudd]

Mark and Joseph discussed this on IRC #wordpress-hackers -- hopefully they summarize it here, but the conclusion is that Mark will work on a patch.

[markjaquith]

Here's the issue:

Windows Live Writer sends dateCreated without the "Z" designating is as a GMT date. WordPress assumes it is a local time, and post_date_gmt gets offset (by the WP-stored GMT offset).

Two things need to happen:

1. Windows Live Writer needs to send the "Z" so we know it's GMT
2. We need to give preference to date_created_gmt (which we can reasonably assume to be GMT even if it lacks the "Z") over dateCreated

Joseph is in contact with the WLW people about the first part, and I've created a patch to do the second part.

[markjaquith]

For Trunk

[lloydbudd]

Generally, we leave Milestone as trunk, until after it has 1st been fixed and vented there.

[ryan]

(In [6691]) Future post publishing over XML-RPC fixes from markjaquith. fixes #5721