Edit report at http://bugs.php.net/bug.php?id=47466&edit=1
ID: 47466
Updated by: philip@php.net
Reported by: kvz@php.net
Summary: Phd seems to ignores .ini timezone
-Status: Assigned
+Status: Feedback
Type: Bug
Package: Doc Build problem
Operating System: Ubuntu Intrepid
PHP Version: Irrelevant
-Assigned To: derick
+Assigned To:
Block user comment: N
Private report: N
New Comment:
I think people here are now confusing PhD with PhP. Also, I think this
bug is
fixed in SVN. :)
@kvz Is this still an issue?
Previous Comments:
------------------------------------------------------------------------
[2011-05-19 17:57:04] demian dot katz at villanova dot edu
I am seeing the same behavior with PHP 5.3.6 built from source on a
RedHat box. I have set an explicit date.timezone value in php.ini, and
I do not see the warning when accessing web pages through Apache.
However, when using the CLI tool, I always see the warning. Running
phpinfo() from the command line confirms that PHP is using the same .ini
file whether accessed via CLI or web and that the date.timezone value IS
being read but is apparently being ignored.
Is there some environment variable that overrides the date.timezone
value? If so, this seems like undesirable behavior.
------------------------------------------------------------------------
[2010-05-27 09:41:02] pjardine at team dot telstra dot com
Same issue. Win server 2003, IIS 6, PHP 5.3.2
Was having problems - PHP info page reported default timezone set
("Australia/Melbourne") but the error was still being logged and the
php_info page reported "no value" in the configured timezone. Opened the
php.ini file in a text editor and saved it as a differnt name. I then
opened a command prompt window and copied the newly save file file to
overwrite the original file. Problem resolved (no more errors, php_info
correctly reporting configured timezone). Not sure why. I did notice
something odd when I initially copied php.ini-production using windows
explorer (I used ^C, ^V to create the copy, then renamed the "Copy of
..." to "php.ini". I ended up with 2 files of the same name, one of
which had a (2) after it. I renamed the files again using windows
explorer (using the date stamp to decide which was which)). Maybe some
odd windows behaviour caused this?
------------------------------------------------------------------------
[2009-10-24 21:10:36] cjm at siegeweb dot co dot uk
Something odd just happened...
I opened php.ini in C:/PHP, deleted all but the line 'date.timezone =
Europe/London' saved, restarted IIS. It didn't work. still got the
warning.
Then I went to that start menu > All Programs > Php. Expanded it and
saw php.ini. Clicked to edit it and got a completely different version
of php.ini (with timezone commented out). Weird (as i thought i'd just
changed that). I verified that the location of the file was
C:/PHP/php.ini - it was. I browsed to C:/PHP/php.ini - opened that
only to see my new version with only the line 'date.timezone =
Europe/London'!? 2 files seemingly at the same location? Saving the
version from the start menu didn't work. So I copied the content of
the full .ini file over to the single line version, changed the
timezone, saved it restarted IIS and timezone warnings have
dissapeared.
------------------------------------------------------------------------
[2009-10-24 20:49:52] cjm at siegeweb dot co dot uk
Same problem for me (php 5.3.0 - IIS 7). Still get warning after setting
the timezone in php.ini. Have verified timezone, tried many others, with
quotes/without quotes. Nothing works, php ignores that line completely.
------------------------------------------------------------------------
[2009-09-01 15:55:02] rod dot lopez at archery-it dot com dot au
I got the same issue on Windows SBS 2003, IIS6, FastCGI, PHP 5.3.0.
php.ini has date.timezone = Australia/ACT, but warning still appears.
If I add <?php date_default_timezone_set('Australia/ACT'); at the
begining warning goes away.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=47466
--
Edit this bug report at http://bugs.php.net/bug.php?id=47466&edit=1