On the screenshots you're showing, I see no inconsistency inside of b2evolution.

At this time, b2evolution does not deal with time zones.

The server time is what the PHP `now()` functions tells b2evolution. If it doesn't match what you want, you can set a "time difference".

I managed to get it to resolve itself by adding this to the php.ini file

date.timezone = "Asia/Riyadh"

It didn't change anything about the way the server itself was displaying its time, but it is now being recognised correctly by b2evo without any need for the time offset.

I guess we should try to display date.timezone on that screen you screenshot.

That would be useful, as it gives positive confirmation of where the server believes it is located. My guess is that most b2evo users won't actually be clear on where there server is, unless they manage it themselves.

I probably should have made it clear earlier that Asia/Riyadh time is +3 hours on GMT/UTC time, not the 2 hours being shown.

Here's our spec, just in case you guys have a better idea / something to add:

That should work great @fplanque