markul

Hi,

I have found the culprit. In the theme I have activated on the problem site there was a line in functions.php:
…
// Let’s set timezone here independently from the server
date_default_timezone_set(‘Europe/Warsaw’);
…

I have no idea why it was affecting the report, since the same was set in WP settings and in the system. Contemplate on this I will…

And thank you for giving me a good direction for diagnosing the problem.

Regards,
Marek

OK, so I will proceed with that.
Please don’t close this thread yet, though I hope migration will do the job ??
Will update you if it was successful.

Here you are:
a:86:… [snip]

Yes, I tried to do all possible checks before bothering you ??
Timezone on both WP is “Warszawa” (Warsaw = UTC+1).
Date format: Y-m-d
Time format: H:i

System-wide:
root@vz13295:~# cat /etc/timezone
Europe/Warsaw

Camu,

Thanks for swift response.
After disabling all other plugins there is no change in described behavior.
The only difference between my two WP sites is that one which is OK is fresh install, and the other had WP SlimStat before. I had to disable it at some point because I had WP 3.5 there, and therefore I couldn’t solve some problems by upgrading your plugin. When I re-installed WP SlimStat (4.2.1) after upgrading WP from 3.5 -> 4.3.1 there was an error (as far as I remember some column was missing in wp_slim_stats table.
I disabled the plugin, dropped all wp_slim_* tables and re-enabled it. It started to show data except the problem for which I have started this thread. Perhaps the upgrade procedure has left some stuff from 3.5 which is affecting date_i18n? If in your opinion there is no better way, I can try to do a fresh install of 4.3.1 and migrate data from my site there, and see if it helps.

Regards,
Marek