It appears that updating to 2.0-b11 introduced a new problem with the server time reports.
I have a website configured to be on the New York timezone. The server time report correctly displays visits at the appropriate time for my timezone in most cases, with a very large exception. In cases where it is near the end of the day in NY, but it is the following day UTC, the report shows the visit for the correct hour in the NY timezone, but displays it for that hour on the following day.
For example, at 22:00 December 11th NY Time, which would be 03:00 December 12th UTC, the server time report is showing that the visit occurred at 22:00 on December 12th. It seems the time is being adjusted appropriately, but the date itself is not. I believe that this is equally affecting standard visit report as well, with visits late in the day being recorded as visits for the following day, but I have not confirmed that and must wait another day to confirm.
These problems did not exist in 1.12. I am unable to provide samples to reproduce this on the demo instance because I do not know what its timezone configuration is, and there must be a deviation between the configured timezone for a site and UTC time in order to see this happen.
I have a website configured to be on the New York timezone. The server time report correctly displays visits at the appropriate time for my timezone in most cases, with a very large exception. In cases where it is near the end of the day in NY, but it is the following day UTC, the report shows the visit for the correct hour in the NY timezone, but displays it for that hour on the following day.
For example, at 22:00 December 11th NY Time, which would be 03:00 December 12th UTC, the server time report is showing that the visit occurred at 22:00 on December 12th. It seems the time is being adjusted appropriately, but the date itself is not. I believe that this is equally affecting standard visit report as well, with visits late in the day being recorded as visits for the following day, but I have not confirmed that and must wait another day to confirm.
These problems did not exist in 1.12. I am unable to provide samples to reproduce this on the demo instance because I do not know what its timezone configuration is, and there must be a deviation between the configured timezone for a site and UTC time in order to see this happen.