Comments on: WordPress 2.2 Reporting Incorrect Time http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time The Weblog of Erik J. Barzeski Tue, 07 Feb 2012 16:40:07 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Andreas http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41614 Andreas Wed, 23 May 2007 13:47:09 +0000 http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41614 What is it with WordPress? I remember there was a similar bug not long ago, maybe 2.1 or something, which was also fixed in a subsequent point release. Guess I'll just wait for 2.2.1 :) Not a major issue anyways. Thanks for the heads-up though! What is it with WordPress? I remember there was a similar bug not long ago, maybe 2.1 or something, which was also fixed in a subsequent point release. Guess I'll just wait for 2.2.1 :) Not a major issue anyways. Thanks for the heads-up though!

]]> By: Mark Jaquith http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41605 Mark Jaquith Tue, 22 May 2007 20:01:50 +0000 http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41605 Got both fixes <a href="http://trac.wordpress.org/log/?action=stop_on_copy&rev=5514&stop_rev=5511&mode=stop_on_copy&verbose=on">into WP core</a> (in trunk and 2.2 branches). Fixes will appear in 2.2.1 and 2.3. Good work, team. :-) Got both fixes into WP core (in trunk and 2.2 branches). Fixes will appear in 2.2.1 and 2.3. Good work, team. :-)

]]> By: Joseph Scott http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41604 Joseph Scott Tue, 22 May 2007 18:42:15 +0000 http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41604 I've updated the ticket with the simple patch we talked about. WordPress.com blogs are already fixed, and I'm working on getting it into the WordPress.org code. I've updated the ticket with the simple patch we talked about. WordPress.com blogs are already fixed, and I'm working on getting it into the WordPress.org code.

]]> By: Erik J. Barzeski http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41601 Erik J. Barzeski Tue, 22 May 2007 16:28:03 +0000 http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41601 [quote comment="41599"]Thank you for reporting <a href="http://trac.wordpress.org/ticket/4314">Ticket #4314</a> 2.2 Reports Incorrect/Malformed Time.[/quote] I've edited the entry above to more properly link to that entry. My blog post was a bit of a "fact-gathering" post, not a bug-reporting post. As you know, Lloyd, I'm happy to post bugs after I gather more facts than "this doesn't seem to work." Lloyd Budd said on May 22, 2007:

Thank you for reporting Ticket #4314 2.2 Reports Incorrect/Malformed Time.

I've edited the entry above to more properly link to that entry. My blog post was a bit of a "fact-gathering" post, not a bug-reporting post. As you know, Lloyd, I'm happy to post bugs after I gather more facts than "this doesn't seem to work."

]]> By: Lloyd Budd http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41599 Lloyd Budd Tue, 22 May 2007 16:02:14 +0000 http://nslog.com/2007/05/22/wordpress_22_reporting_incorrect_time#comment-41599 Thank you for reporting <a href="http://trac.wordpress.org/ticket/4314">Ticket #4314</a> 2.2 Reports Incorrect/Malformed Time . I think you are correct as to the origin of this issue as described in that ticket. I will talk to Joseph Scott who did this related work for XML-RPC in WordPress 2.2 and WordPress.com . I am near certain that the issue is not the '-', because that topic previously came up, and both formats are accepted in this context. Thank you for reporting Ticket #4314 2.2 Reports Incorrect/Malformed Time . I think you are correct as to the origin of this issue as described in that ticket.

I will talk to Joseph Scott who did this related work for XML-RPC in WordPress 2.2 and WordPress.com .

I am near certain that the issue is not the '-', because that topic previously came up, and both formats are accepted in this context.

]]>