Edit report at https://bugs.php.net/bug.php?id=40743&edit=1
ID: 40743
Comment by: kavi at postpro dot net
Reported by: ddb at bitxtender dot de
Summary: DateTime ignores the TimeZone object passed to the
constructor
Status: Closed
Type: Bug
Package: Date/time related
Operating System: Win XP
PHP Version: 5.2.1
Assigned To: derick
Block user comment: N
Private report: N
New Comment:
This bug is NOT fixed on 5.3.3 or trunk.
$ php
<?php
$a = new DateTime('Monday, 15-Aug-05 15:52:01 PDT', new
DateTimeZone('America/New_York'));
print_r($a);
DateTime Object
(
[date] => 2005-08-15 15:52:01
[timezone_type] => 2
[timezone] => PDT
)
Previous Comments:
------------------------------------------------------------------------
[2008-01-17 18:50:12] [email protected]
This bug has been fixed in CVS.
Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
Thank you for the report, and for helping us make PHP better.
------------------------------------------------------------------------
[2007-04-19 20:53:33] artur at jedlinski dot pl
It is ignoring the #2 parameter when you put the timezone info inside the #1.
It's *absolutely* unacceptable.
// Europe/Warsaw = GMT +0200
$dateSrc = '2007-04-19 12:50:00 GMT';
$dateTime = new DateTime($dateSrc, new DateTimeZone('Europe/Warsaw'));
echo $dateTime->format('H:i:s')."<br />";
// RESULT: 12:50:00 (expected: 14:50:00)
$dateTime->setTimeZone(new DateTimeZone('Europe/Warsaw'));
echo $dateTime->format('H:i:s')."<br />";
// RESULT: 14:50:00 (correct)
IMHO the most intuitive way is to create the date based on the #1, but displays
it using #2.
It's not only strange it ignores #2, but in fact it's strange that the internal
DateTime pointer is set to timezone provided in #1 at all. If the
date_default_timezone_set() was set to some TZ, it should create dates within
this timezone if one doesn't state otherwise (using #2). Of course the timezone
info from #1 should be used, but only to calculate the actual timestamp.
date_default_timezone_set('Europe/Warsaw');
$dateSrc = '2007-04-19 12:50:00 GMT';
$dateTime = new DateTime($dateSrc);
echo $dateTime->format('H:i:s')."<br />";
// RESULT: 12:50:00 (expected: 14:50:00)
Currently, it's pretty complicated to translate dates from one timezone to
another - you have to use DateTime::setTimeZone(), when one line should do the
thing:
$dateTime = new DateTime($dateWithSrcTimeZone, $timeZoneToDisplay);
(or even without $timeZoneToDisplay if you want to use your current TZ).
------------------------------------------------------------------------
[2007-04-11 14:45:46] [email protected]
It's not totally ignored, but something fishy is going on. See the following
script + output:
<?php
$dt = new DateTime();
echo $dt->format(DATE_RFC822 . " e T O"), "\n";
$dt = new DateTime('@' . time());
echo $dt->format(DATE_RFC822 . " e T O"), "\n";
$dt = new DateTime('@' . time(), new DateTimeZone('Europe/Berlin'));
echo $dt->format(DATE_RFC822 . " e T O"), "\n";
?>
Wed, 11 Apr 07 16:42:40 +0200 Europe/Oslo CEST +0200
Wed, 11 Apr 07 14:42:40 +0100 Europe/Oslo GMT+0100 +0100
Wed, 11 Apr 07 14:42:40 +0100 Europe/Berlin GMT+0100 +0100
------------------------------------------------------------------------
[2007-03-06 23:27:24] ddb at bitxtender dot de
Description:
------------
when you create a new DateTime object the timezone object you pass along in the
constructor is ignored.
setting the timezone using setTimeZone works as expected.
also tested with 5.2-dev and 6.0-dev
Reproduce code:
---------------
$dt = new DateTime('@' . time(), new DateTimeZone('Europe/Berlin'));
echo $dt->format(DATE_RFC822);
Expected result:
----------------
Tue, 07 Mar 07 01:22:55 +0100
Actual result:
--------------
Tue, 07 Mar 07 00:22:55 +0000
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=40743&edit=1
