#50839 [NoF->Opn]: log_errors + display_errors = bogus timezone warning in response entity
ID: 50839
User updated by: miqrogroove at gmail dot com
Reported By: miqrogroove at gmail dot com
-Status: No Feedback
+Status: Open
Bug Type: PHP options/info functions
Operating System: Windows 2003
PHP Version: 5.3.1
New Comment:
Please keep this bug open.
Previous Comments:
------------------------------------------------------------------------
[2010-02-26 06:23:57] miqrogroove at gmail dot com
Please keep this bug open.
------------------------------------------------------------------------
[2010-02-03 01:00:00] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2010-01-27 06:26:49] miqrogroove at gmail dot com
> you should actually read the error message and do what it suggests?
As a developer, I don't have the luxury of assuming servers are
configured a certain way. Since PHP offers no way to check if the
default timezone has been set already, the only alternative I have is
to
disable error reporting, so that functions like mail() wont interrupt
header output or image generation.
If you do find that Windows snapshot for me, could you check if it
comes
with the installer, or if there are any instructions for upgrading
without the installer?
------------------------------------------------------------------------
[2010-01-27 02:03:36] miqrogroove at gmail dot com
hi jani,
I followed your link and all it says is:
PHP 5.3
5.3 has no release.
PHP 5.2
5.2 has no release.
PHP 6.0
6.0 has no release.
------------------------------------------------------------------------
[2010-01-26 07:27:40] jani@php.net
Please try using this snapshot:
http://snaps.php.net/php5.3-latest.tar.gz
For Windows:
http://windows.php.net/snapshots/
IIRC, this was fixed already..then again, you should actually read the
error message and do what it suggests? :)
------------------------------------------------------------------------
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/50839
--
Edit this bug report at http://bugs.php.net/?id=50839&edit=1
Thread (9 messages)