My dev server (MAMP running on a mini) PHP
Default timezone America/Halifax
date.timezone local value: America/Halifax master value: America/Halifax
I did set this but long before this problem occurred. I also removed the values at one point while trying to fix the issue but I've never touched MySQL settings as far as I know by default MySQL will use system time.
http://dev.mysql.com/doc/refman/5.5/en/time-zone-support.html
I did have the same issue on a production server when I upgraded to 2.2.0 It has:
Default timezone America/New York
date.timezone local value: (no value) master value: (no value)
That's on a shared host so I had no control over timezone settings. When I talked to tech support they said that both PHP and MySQL should be getting time zone values from system time. So there should never be a problem with them being synced. (big grain of salt)
I'm not sure what fixed that one unfortunately. I was furiously trying to get things done as it was a production server. The last thing I did was removed the Modx timezone setting in system settings. Not sure if that's what did it but it certainly seemed like it. At the time it looked like THE solution but left me wondering what the point of that setting was if it couldn't be changed. When I ran into the same issue on my dev server and there was no value in time zone system settings my confidence in that solution waned a bit.
On production server install I do have a server offset value in system settings of 1 but nothing in timezone. In the system report I get the right times for local and server but oddly Quip still uses the timezone and ignores the server offset. That's another issue though.
The long and short is that nothing I did to the time zone settings on the server seemed to have any bearing on this issue. I may be wrong but it seems to be a Modx problem. Maybe it's not one that shows up all the time but when it shows up it's huge.
[ed. note: kevince52 last edited this post 12 years, 1 month ago.]