Comments on: WordPress 2.9 – When’s the Time Zone Set? http://nslog.com/2009/12/24/wordpress_29_when_is_time_zone_set The Weblog of Erik J. Barzeski Tue, 07 Feb 2012 16:40:07 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Simon Tsui // WordPress 2.9.1 fails to address time zone problem http://nslog.com/2009/12/24/wordpress_29_when_is_time_zone_set#comment-56688 Simon Tsui // WordPress 2.9.1 fails to address time zone problem Wed, 06 Jan 2010 08:24:55 +0000 http://nslog.com/?p=6610#comment-56688 [...] the advice that I used from NSLog();'s post about WordPress still [...] [...] the advice that I used from NSLog();'s post about WordPress still [...]

]]> By: Simon Tsui // Holiday RAGE: WordPress, 1&1 and the Time Zone Problem http://nslog.com/2009/12/24/wordpress_29_when_is_time_zone_set#comment-56596 Simon Tsui // Holiday RAGE: WordPress, 1&1 and the Time Zone Problem Wed, 30 Dec 2009 21:00:11 +0000 http://nslog.com/?p=6610#comment-56596 [...] time-zone settings within WordPress and it seemed correct. Today, I was referred to a blog post: WordPress 2.9 – When’s the Time Zone Set? which confirmed my suspicions AND resolved the [...] [...] time-zone settings within WordPress and it seemed correct. Today, I was referred to a blog post: WordPress 2.9 – When’s the Time Zone Set? which confirmed my suspicions AND resolved the [...]

]]> By: Simon Tsui http://nslog.com/2009/12/24/wordpress_29_when_is_time_zone_set#comment-56595 Simon Tsui Wed, 30 Dec 2009 19:58:31 +0000 http://nslog.com/?p=6610#comment-56595 Todd and Erik, you both are lifesavers! I spent the entire week fuming over my website's broken PHP script and calling 1&1's Customer Service to complain that they screwed around with my domain's server. They kept telling me that it was my own code's fault, and when I backtracked through the past week's events, I realized the WordPress 2.9 update occurred around then too. I had my suspicions about WordPress. Todd and Erik, you both are lifesavers! I spent the entire week fuming over my website's broken PHP script and calling 1&1's Customer Service to complain that they screwed around with my domain's server.

They kept telling me that it was my own code's fault, and when I backtracked through the past week's events, I realized the WordPress 2.9 update occurred around then too. I had my suspicions about WordPress.

]]> By: Erik J. Barzeski http://nslog.com/2009/12/24/wordpress_29_when_is_time_zone_set#comment-56578 Erik J. Barzeski Tue, 29 Dec 2009 19:25:08 +0000 http://nslog.com/?p=6610#comment-56578 [quote comment="56577"]Comment out the 'if' statement (lines 21 & 22) in this file, and everything should work properly, without having to set the timezone in your header.[/quote] That did it. Awesome. I wonder if they consider this a bug… I'll have to go check and will consider filing one. It'll be a real pain to change that every time a new version of WordPress comes out. (TRAC <a href="http://core.trac.wordpress.org/ticket/11665">#11665</a>.) Todd Brandys said on December 29, 2009:

Comment out the 'if' statement (lines 21 & 22) in this file, and everything should work properly, without having to set the timezone in your header.

That did it. Awesome. I wonder if they consider this a bug… I'll have to go check and will consider filing one. It'll be a real pain to change that every time a new version of WordPress comes out. (TRAC #11665.)

]]> By: Todd Brandys http://nslog.com/2009/12/24/wordpress_29_when_is_time_zone_set#comment-56577 Todd Brandys Tue, 29 Dec 2009 18:41:28 +0000 http://nslog.com/?p=6610#comment-56577 I was having the same problem. If you look in the wp-settings.php file, you'll find that the default timezone is set to 'UTC'. This is what is causing the time discrepancy. Comment out the 'if' statement (lines 21 & 22) in this file, and everything should work properly, without having to set the timezone in your header. I was having the same problem. If you look in the wp-settings.php file, you'll find that the default timezone is set to 'UTC'. This is what is causing the time discrepancy. Comment out the 'if' statement (lines 21 & 22) in this file, and everything should work properly, without having to set the timezone in your header.

]]>