10389 Posts in 2200 Topics by 1712 members
Page: 1 2
|Go to End|
10 January 2010 at 4:06am
Ok... i'm getting a bit closer to at least figuring out what the interruption in dates is!
It has to do with my system, and how dates are retrieved -- back to your original thought on an 'incorrect date' gives that 1969 result.
That said... after I saved the events from my previous post, then went back to look at them... this is what I saw:
See? I think it's taking the dates entered (example in myd) 01/01/2010 as Jan 01, 2010. however I think it's taking 01/02/2010 as Feb 01, 2010, instead of Jan 2, 2010 ... Am I right? That makes sense, as dates entered from the 13th and beyond wind up with the 1969 year!
So, the underlying question now is "WTF" does it do that?
Sure hope this helps.
10 January 2010 at 4:21am
Ok, so tried changing my _config from dmy to mdy...
Looks to be the same thing.
Not much more I think I can figure to test... so I'll await your response
10 January 2010 at 4:34am
MWAHAHAHA !!! I got it!
I saw this thread: http://www.silverstripe.org/all-other-modules/show/268928#post268928 where you said the following:
Make sure you're using
CalendarDateTime::set_date_format('mdy') // or "dmy"
CalendarDateTime::set_time_format("12") // or "24"
DatePickerField::set_date_format('mdy') // or 'dmy'
I noticed where my _config did not have the DatePickerField ... so I went ahead and set mine to match my CalendarDateTime::set_date_format...
Hope this helps others... And thanks again UncleCheese for such a great module!
Page: 1 2
|Go to Top|