Thread

I’m finding that if I set the entry_date or expiration_date to a month in the future that the date field reduces by an hour on every save.

For example if it’s currently March and I set the expiration_date to sometime in April, when I save the entry the date is reduced by 1 hour. The same thing applies to the entry_date. It’s fine if it’s set in the past or to the current month.

I’ve confirmed this on a clean install of ee 2.1.3 Build 20101220. My timezone is set to +10. It happens whether daylight savings is set to yes or no.

I’m working on a website that includes events and needs to launch very soon so any help would be greatly appreciated.

Hi, superbiaweb - it’s a bug in the date routines of both EE2.1.3 and EE2.1.4beta. Can you test with an entry in November of this year? That would be outside the DST stuff.

Yes it doesn’t happen if the dates are in November. Is there anything that can be done to fix this? Can a patch be released? I have about 5 sites on 2.1.3 and would really like to resolve this.

Thanks

Dylan

It’s still broken in EE2.1.4beta, although the dev team believes they have a possible fix for the full release. I’ll ask. Thanks in advance for your patience.

Solspace’s Calendar module date fields don’t seem to suffer from this so I’ll see if I can use it instead. If a patch can be released it would be really appreciated as this affects a number of live websites.

This appears to fix the problem:
https://support.ellislab.com/bugs/detail/15202/

That would be the one. So you implemented it in 2.1.3 successfully? In that case, I’ll recommend it if others run into a similar issue.

Sorry for the late reply. Yes the fix in the bug report appears to solve the problem I was having in 2.1.3. It should be applied to a file called ‘Localize.php’ not ‘Localization.php’.

Thanks superbiaweb. We’re working on this for the next release. Closing this but don’t hesitate to post again.