It should render the time at the location that is specified, however the user notices that there is Daylight saving time activated even in countries that don't observe this.
Solution:
The user had set a specific timezone in their wordpress settings to a location that observes Daylight Saving Time. This had the effect that it will offset all the clock location by the DST rules.
To workaround this I would recommend setting your wordpress settings timezone to UTC or GMT with no offsets.
This support ticket is created 5 years, 7 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Ever since Daylight Saving Time has started, all the times shown using this are 1 hour ahead of the actual time. I have tested and both the server and WordPress are showing the correct times so I cannot see what is causing this all of a sudden.
I think I may be able to best explain with a few examples below.
Europe/London for London actual time is 16:50 showing 17:50
Asia/Beirut for Beirut actual time is 18:50 showing 19:50
Australia/Brisbane for Brisbane actual time is 01:50 showing 02:50
This is interesting because Brisbane doesn't use any DST.
I have spoken to them already and it works as expected for them.
Is there any way you can set up a test your side using the exact code I used above and then define the timezones using a custom field as I do and see if that affects results in any way?
So all the times that you see on the site will be posted in the time relative to the GMT time.
If you have it at GMT right now, when you create a post it will set the time relative to GMT.
What i believe is happening is that wordpress has an internal system that has a list of timezones that observe DST and is setting the offsets based on this.