Bug #47466 [Com]: Phd seems to ignores .ini timezone
| From: | xmoravka at seznam dot cz | Date: | Sun, 02 Oct 2011 02:06:27 +0000 |
| Subject: | Bug #47466 [Com]: Phd seems to ignores .ini timezone | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-7287@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=47466&edit=1
ID: 47466
Comment by: xmoravka at seznam dot cz
Reported by: kvz@php.net
Summary: Phd seems to ignores .ini timezone
Status: Closed
Type: Bug
Package: Doc Build problem
Operating System: Ubuntu Intrepid
PHP Version: Irrelevant
Assigned To: philip
Block user comment: N
Private report: N
New Comment:
I found out that date.timezone option is without any effect, if php finds any syntax error on any
row in php.ini file.
Previous Comments:
------------------------------------------------------------------------
[2011-06-07 15:40:37] philip@php.net
Thank you for the open and honest reply, and this happens (and will continue to
[occasionally] happen) to all of us. :)
------------------------------------------------------------------------
[2011-06-07 15:32:34] demian dot katz at villanova dot edu
First of all, apologies for being confused about Phd vs. PHP -- I assumed since this is a bug
tracker on PHP.net that it was simply a typo in the heading!
Secondly, my bug turns out to be a simple typo in the .ini file -- despite the fact that I checked
and triple checked, I missed the fact that I had a space in place of an underscore! Still a mystery
why the CLI version complained more persistently about this than the Apache version, but I'm
not too concerned.
Once again, sorry for putting this in the wrong place AND complaining about a bug that was really
just my own bad eyes -- but I figured I might as well bring closure to the issue in the same place I
brought it up, just in case somebody else finds themselves following the same path that I did.
------------------------------------------------------------------------
[2011-05-19 18:30:37] philip@php.net
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?
------------------------------------------------------------------------
[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?
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=47466
--
Edit this bug report at https://bugs.php.net/bug.php?id=47466&edit=1