Hi
I still get warning from phpMyAdmin about timezones:
Warning in ./libraries/common.inc.php#291 date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead
Backtrace
./libraries/common.inc.php#291: date_default_timezone_get() ./main.php#13: require_once(./libraries/common.inc.php)
And I started to think if it would not be better to make timezone our configuration (in config and in store it in cookie) with default to UTC to get rid of this warning.
I know this can be fixed by changing php.ini, but there is lot of people who can not do it.
Michal Čihař wrote:
Hi
I still get warning from phpMyAdmin about timezones:
Warning in ./libraries/common.inc.php#291 date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead
Backtrace
./libraries/common.inc.php#291: date_default_timezone_get() ./main.php#13: require_once(./libraries/common.inc.php)
And I started to think if it would not be better to make timezone our configuration (in config and in store it in cookie) with default to UTC to get rid of this warning.
I know this can be fixed by changing php.ini, but there is lot of people who can not do it.
As long as someone with a good php.ini does not have to 'fix' it again in the pma config I would be fine with it. But can we determine with some certainty that the php config is correct?
Hi
Dne Wed, 13 Jan 2010 11:30:44 +0100 Herman van Rink rink@initfour.nl napsal(a):
As long as someone with a good php.ini does not have to 'fix' it again in the pma config I would be fine with it. But can we determine with some certainty that the php config is correct?
Probably not without warning (maybe output buffering could be used to hide it, but I feel it is ugly).
Michal Čihař a écrit :
Hi
I still get warning from phpMyAdmin about timezones:
Warning in ./libraries/common.inc.php#291 date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead
Backtrace
./libraries/common.inc.php#291: date_default_timezone_get() ./main.php#13: require_once(./libraries/common.inc.php)
And I started to think if it would not be better to make timezone our configuration (in config and in store it in cookie) with default to UTC to get rid of this warning.
I know this can be fixed by changing php.ini, but there is lot of people who can not do it.
Michal, I think you are getting these warnings because you want to. Your error handler display configuration is set to true, which is not the default setting.
The warning is just on login page, right?
Marc
Hi
Dne Thu, 14 Jan 2010 06:22:19 -0500 Marc Delisle marc@infomarc.info napsal(a):
I think you are getting these warnings because you want to. Your error handler display configuration is set to true, which is not the default setting.
You're right, however I still think this warning should not be emitted.
The warning is just on login page, right?
It's also on main page and maybe on others.