[wp-hackers] Daylight Savings Glitch
eric at eamann.com
Mon Mar 15 17:43:38 UTC 2010
Actually, changing the post time and changing the post status to "publish"
rather than "future" published the post. In any case, even if this was an
issue with wp-cron, it shouldn't have happened. Any ideas on how to make
WordPress sensitive to the fact that I was scheduling a post for after
From: wp-hackers-bounces at lists.automattic.com
[mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Otto
Sent: Monday, March 15, 2010 10:14 AM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] Daylight Savings Glitch
If you had waited until 10am, I think it would have posted. What was
probably happening was that the scheduled event in wp-cron to post the
job had not fired yet.
BTW, the time in the posts table was correct. You should not have
changed it, nor do I think it would have made any difference, really.
The time in the post controls nothing, the wp-cronjob controls when
the post publishes.
On Mon, Mar 15, 2010 at 11:55 AM, Eric Mann <eric at eamann.com> wrote:
> Actually, I just investigated further. It appears that any post I saved
> before Daylight Savings Time inherited the pre-savings UTC settings. So
> = 17:00 before Daylight Savings went into effect. I checked the wp_posts
> table and updated things accordingly (setting the post time to 16:00
> of 17:00). This doesn't seem to be so much of a bug as it does an
> ... publishing should work just fine from here on out, but is there a way
> patch this in the future to prevent this kind of behavior?
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers