Hi,

I am still trying to sort out this whole DST thing, some progress has been made but I’m still not there.

I am generating a VCS file so people can import events into Outlook etc. I have now used the gmt_entry_date for the start date and it seems to be working ok, I am currently in DST so when I post a new event the entry_date time stamp in the database is 1 hour behind what I entered and gets imported to outlook correctly.

For the end date I am using a custom date field set to localized, this is where I’m loosing it because the timestamp for this field in the databases shows as being 2 hours behind what was entered when the event was posted to the weblog.

One plan would be to just add an hour to this timestamp but I’m not sure how this could affect things in the future.

And advice here would be much appreciated.

EE 1.6.8

Thanks
Matt

worldig, DST settings can be confusing.

What I usually do is to uncheck DST Active on Date of Entry.

If you do that, what happens?

Hi as far as I can see its never ticked anyway, if i make a post the entry date seems to be entered in the database as 1 hour behind which I would expect but the DST setting is always set to ‘n’.

Toggling the DST setting under options does not seem to do much apart from update the field in the db to ‘y’.

Its the custom date field that seems to be out if I enter say 12:00PM then convert the time stamp entered in the db it would be 10:00AM where I would expect it to be 11:00AM which would make it GMT and in line with the entry date.

What’s the value of Default timezone in your PHP Info settings?

I’m going to be testing this behavior on my server where I’m in the same time zone as the server. What about you? How do your settings compare to the server?

Hi,
In my php: Default timezone   Europe/London
My laptop is also in the same timezone.

It seems weird that its ok with the entry_date but not with the custom date field

I see what you mean. I’ll check with the dev team and see what I can find out.

The date entered into the db for both the entry_date and the custom field date should be gmt in both cases.  From there- the various settings influence how the date will be displayed. 

If I understand correctly- try putting the custom field in as ‘fixed’ to the actual date you want it-.  It shouldn’t vary, shouldn’t be localized.  I think that’s what you’re going for.

Unless the problem is actually the dates as entered into the db.  I THINK what you’re running into is a presentation/localization issue, though.

Hi,

If I set the custom field to fixed the timestamp in the db is still 2 hours behind what is entered in the weblog field at publish time.

Taking a look at some articles that were entered when dst was not active the timestamps for these seem to be 1 hour behind what was entered which would make them GMT-1 which also seems a bit strange.

It seems consistent so I can just add 1 hour to the timestamp when I pull it from the db but it doesn’t seem correct :s

Thanks
Matt

How do you enter these dates? Via the control panel? Which user does it, does he have localization set?

Hi,

I am logged in as the admin user, super admins group, local settings are set to GMT for this user.

Yes the dates are being entered through a custom date field in the control panel.

Thanks
Matt

Sorry this is dragging out, Matt.  Fixed time isn’t acting quite as I’d expect it to- so I’m doing some poking.  Oh- and just so I’m dead sure what’s up- all the dates we’re talking about are being parsed via a weblog tag- and date formatted.  You’re not pulling directly from the db.  Correct?

Hi sorry for the late reply here,

Yes they are being pulled with a weblog tag from a custom date field.

{entry_date} is ok the timestamp is always GMT

{custom_date} is not and in the db the timestamp always translates to 2 hours behind what was entered so essentially GMT-1

Thanks
Matt

Bleh-  ok, even if ‘fixed’, the date fields will vary based on DST settings- which is what I suspect you’re seeing. 

What do your date tags look like- entry date and the custom field (i.e. when used on the templates).

And the goal is- to have a date that doesn’t vary irregardless of server DST and individual localization?

Hi,

Tags Below:

That’s how they are in the template now anyway I’ve tried so many different ways no I loose track.

Ideally I would just like it to display GMT+0 all the time.

Thanks
Matt

Hi, Matt,

I apologize for the delay on this one.  It is something we are working on internally but may take some time for us to work through.  I thank you for your patience and we’ll follow up with you as soon as we have more information.

Just had a situation tonight where a calendar entry is showing different dates to different people because of the localisation and the entry time (just past midnight!) and am working through that right now so I am looking forward to the reply from Lisa and crew as well.

Hi,

Just wondering if there’s any more info on this yet?

Thanks
Matt

Hi, Matt. I apologize for the time it’s taken to get back to you. Our development team is less than a week away from launching EE2.0RC. I’ll go ask, and let you know what I find out. Thanks in advance for your patience.

Hi, Matt - as Sue said, our development is hard at work to be ready by December 1st.  I know that this has also been worked on and we’ll have more information for you as soon as possible, but may not be before early next week.

My apologies for the delay on this.