I’ve actually changed the format that the date picker uses to be dd-mm-yyyy and it’s working great! Issue solved. Jim
Be interested to know how - was it hacking the EE source files?
Edit: Assume this was referencing the output in the template using “format” and not how it’s displayed in the publish tab :(
Want to say thanks a bunch for this ext. it’s helped a lot.
That being said, I’ve run into an odd snag with DST and even just regular date processing be it in SAEF or CC. See posts in this thread for details, but the gist is that localization settings are being overridden and times are getting decremented 1 hour, even though the dates are for DST active (which should be 1hour ahead, spring forward/fall behind).
Again this is for an entry whose entry/expire dates are after DST goes active, but entry is being submitted prior to DST being active. I can’t test until after Sunday if the glitch occurs after the server starts observing DST.
After a couple of more tests, the problem I related seems to be specifically when you are entering an entry for a date opposite DST setting currently held in the system. So in the example above I was pre-March 14th entering an entry March 20th. After the 14th, re-adding/editing the same entry no problem. Now I can recreate by trying to add an entry Nov8th (DST no longer active) and the problem re-appears. This could still possibly be a combo of my localization settings, but its nothing fancy.
This issue affects the time entered on a fixed/local custom field as well, however, there seems to be an oddity in EE 1.6.8 (or a combo of specific localization settings I’ve yet to figure out) with this as well regardless of Blinddate is enabled or not. Again see this thread.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.