This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
August 30, 2011 2:15pm
Subscribe [3]#1 / Aug 30, 2011 2:15pm
This question may be related to a resolved thread.
Apparently, my problem in the linked thread wasn’t fixed by setting DST to No.
I’ve avoided the problem by breaking the time into a separate, hard-coded drop down that is completely unrelated to the actual date/time. There still seems to be no way to have EE ignore DST (and localization) so that if the author posts at 7:00 am, the entry date will always be 7:00 am, regardless of the time of year, DST or the viewer’s time zone.
#2 / Aug 31, 2011 3:05am
Hi aircrash,
To confirm. What about your own account localization settings. What are they set at presently?
Or the author. If you login as them what is their DST set at?
#3 / Aug 31, 2011 9:49am
In my account, DST was set to Yes, the author’s account was set to No, but we both had the problem.
#4 / Sep 02, 2011 11:37am
Hi aircrash,
I thought the solution in the previous thread was to make sure everyone has DST set to “No” and leave it that way. Does the problem still present itself if you turn off your DST and post a new entry?
#5 / Sep 02, 2011 12:51pm
Kevin, I think you’re right. The problem was with dates that had already been posted. When I turned off DST, everything was off by an hour; and having users in different time zones just complicated things more.
The solution seems to be turning DST off for everyone FROM THE BEGINNING. Changing the DST settings after entries have been posted causes all sorts of trouble. I’ve had to go back and manually change the times for dozens of entries.
#6 / Sep 03, 2011 12:46am
Yep, for now it looks like the solution is to turn off DST for everyone from the beginning and to make sure your entries don’t have DST enabled either. If you’re feeling up for it, you could ensure DST is disabled in all your entries by taking a look at the ‘dst_enabled’ field of the ‘exp_channel_titles’ table. This should go without saying, of course, but PLEASE have a backup of your database before messing around directly in it. Since dates are stored in the DB at proper Unix timestamps (read: UTC), that should clear up the issues you’re having. If not, that will at least ensure that your entries are now set to have DST which means that your entire system will be all using the same reference point with regard to time.
For a longer term fix, I’d love to hear your own suggestions for how the user experience should be regarding dealing with dates, times, and timezones. I can’t promise anything except that we’re listening, but we do want to hear you.