Thread

This question may be related to a resolved thread.

Hi,

I am running EE 2.2.1, build 20110630.

Right now here in Germany it’s daylight-saving time. In my own admin-account I have time-zone utc+1 and DST set to “yes”.
In the Admin->Localization-Settings I have UTC+1, Server-Offset nothing, DST “yes”.
I checked that the servertime is correct.

Now I posted an entry; in the backend the date of the entry is 14.18, on my watch it is 14.18 - but in the frontend the entry is set to 13.18 (regardless if I am logged in or not).

Is there any hint?

Thanks in advance!

Hey lehrerfreund,

I’m sure this is pretty frustrating. Is this behavior consistent every time you post an entry? Have you been able to find a pattern to when it happens? Does it happen with every channel or just particular channels? Is this on a publicly-accessible server? We may need to hop in there and see what’s going on.

Hi Kevin,

it happens all the time. I have got two channels, in both the same issue.
I gladly will give you the login-data, if you want to take a look.

Hi there lehrerfreund,

I’ll get the login ball rolling. Be on the lookout for an email form me.

Best,

Hi Daniel,

form submitted. If you urgently need to publish a test-entry please use the channel “tech”. But I would be glad if you would not need to.

Thanks already now for your effort!

Daniel,

I don’t know if you already have changed something; right now I published an entry and the time was correct. I myself definitely did not change anything with the configuration since the last entry I published and which came up with the wrong time.

Hi lehrerfreund,

No, to my knowledge, no one had logged in or changed anything on your site. Can you make a few more test entries and verify that they come up with the correct time?

Thanks,

I did another test-entry and the time was correct. Perhaps just giving you the login-data did the trick?

Seriously: I swear I did not change anything. So this is a mysterium.

Perhaps we could leave open this entry for some days until I confirm that it works permanently; I will post here again when I have seen more.

Anyway: Thanks for your helping presence 😊

Hi,

I just launched an entry and again the time is one hour too early.
I just tried at the other channel and the problem was the same.

So well ... the login-data still is available for you, if you want to have a look ...

Hello Lehrerfrund,

We should have verified this first, but In Admin-> Localization Setting is “Server Time Zone” set to the correct time zone? Note: this setting reflects the time zone where your server is located, not the time zone *you* are in, although they very well could be the same.

Thanks for your patience,

Hi Dan,

yes, Server Time Zone is correct, the Server is located in Germany - at least they tell me this.
If this would be the reason for the 1 hour-delay, then it would ALWAYS not work (and not, as my last 2 posts show, only sometimes/mostly ... ).

Would have been an easy solution 😊

Just confirmed with the admin: The server is located in the same timezone as I myself.

Hi lehrerfreund,

Thank you for checking that for us. What about Daylight Savings Time? The discussion in this thread seems very similar and could be related. Can you double check your DST settings and see if that clears this up for you?

Thanks,

Dan, I double checked and as stated in my initial entry both DST-settings seem to be correct.
Right now I launched an entry. My clock shows 10.47, my server-time is 10.47, the time of the entry is set to 10.47 - but in the frontend there is 9.47.
In the Database (exp_channel_titles) i finde 1311756440 as entry_date, which also is 10.47. If you go to the entry you will see that it is set to 9.47 ( http://www.lehrerfreund.de/in/schule/1s/halluzinationen-kaffee/3950/ ). See screenshots attached.

So everything smells like only some setting is wrong - but which?!

Hi lehrerfreund,

The consistent behavior I’ve been able to determine is this: When logged in to the Super Admin account, the time displayed on the front-end is correct. When not logged in to any account, the time displayed on the front-end is an hour behind. Can you confirm that this the same behavior you’re experiencing?

I’m not able to replicate this locally, so it doesn’t appear to be a bug in the code. The behavior does appear to be consistent on your site, though, so let’s keep digging to figure this out. I’ll wait to hear back from you to make sure we’re on the same page regarding the problematic time offset and exactly when it occurs.