-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does MODX need the PHP setting "date.timezone" to work? #57
Comments
This is php 5.3 config, not MODX. The error could be better and more Quick search: http://forum.joomla.org/viewtopic.php?t=363681 |
Thanks, @Mark-H. Yes, it's a malconfigured system (PHP) that causes the error, not MODX itself. But why is date.timezone so important? What does "It is not safe to rely on the system's timezone settings." mean? Not save? Why can't the system live with the "UTC" fallback? |
Also: http://stackoverflow.com/questions/22785828/why-does-php-think-its-a-bad-idea-to-rely-on-the-systems-time-zone
|
I just try to imagine a webserver on a plane doing international flights. :-) |
Many things subtly rely on proper timezones. Everything from profiling More obviously if the server is configured to display errors (given the
|
Leave it as a fact of life @mindeffects 😉 I guess it's better than the alternative of PHP shipping with a default timezone of EST and then new users wondering why it's wrong (though I do wonder why it can't just use the server' timezone by default) |
Read only a few of Marks links... but I still don't understand why we do not set the timezone in setup and core with |
I agree with @inreti – this would be way better than the current fatal error, especially for technically less experienced users. |
:-( ohhh... we have not talked about this issue... damn... |
Instaling MODX on a fresh system is not really much fun, When you have all those apache and other modules I place, you get a slap by the setup for not having set a value for "date.timezone". Besides the harsh "FATAL ERROR" yell you are left alone. OK, the problem lies in the php.ini, but the system not is very helpful here. Took my quite a while to figure out was was going wrong when I first ran into that problem.
I was told that "date.timezone" has to be set, because otherwise MODX would not function correctly. OK, I understand that bad things will happen, but I don't understand why. I also don't understand why other CMSes can perfectly live without a date.timezone setting and don't crumble in to peaces.
Maybe it's just my lack of deeper core knowledge, but wouldn't it be better if the MODX was not depending on date.timezone? There has to be a solution for that!
Can someone explain the logic behind the mandatory date.timezone-setting? I really want to understand the WHY!
The text was updated successfully, but these errors were encountered: