[wp-trac] [WordPress Trac] #10332: Backdated pre-1st January 1970 post displayed as published on the current viewing day

[WordPress Trac]

#10332: Backdated pre-1st January 1970 post displayed as published on the current
viewing day
--------------------------+-------------------------------------------------
 Reporter:  carboncopy    |       Owner:  nacin                                   
     Type:  defect (bug)  |      Status:  accepted                                
 Priority:  high          |   Milestone:  3.1                                     
Component:  Date/Time     |     Version:  2.8                                     
 Severity:  major         |    Keywords:  has-patch needs-testing needs-unit-tests
--------------------------+-------------------------------------------------
Changes (by nacin):

  * keywords:  has-patch needs-testing dev-feedback => has-patch needs-
               testing needs-unit-tests
  * priority:  normal => high
  * status:  reviewing => accepted


Comment:

 Replying to [comment:27 hakre]:
 > Date time with PHP 5.2 is always 64bit regardless of the underlying OS
 IIRC. 32Bit system will use a float in PHP then to handle the timestamp. I
 suggest to upgrade to PHP 5.2 or above to not run into problems.

 Correct, and that's reasonable in WP 3.2. But there's a simple interim fix
 we can do now that will prevent unnecessary limitations in 3.1. The
 problem is, due to our code right now, upgrading to PHP 5.2 won't produce
 the desired result -- the code, as is, takes a lowest common denominator
 approach. Instead of using version_compare(), however, I based this on how
 PHP handles these values in affected versions, which increases the
 coverage (as not all < 5.2 versions are affected).

 I'm going to try to write some unit tests for this and work on it in 3.1.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/10332#comment:29>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software