Basically what happens is when you try to create a new calendar item, when altering the Start and End times, there is some sort of bug occurring in how it calculates the time codes in the back end. If the times of the event start in the AM and end in the PM, it causes some sort of issue with the way the timecodes are calculated. As well, it appears to be an issue with the 'predictive' functionality it uses. When you select something like an 8AM Start time, it will automatically try to adjust the End time to something an hour in advance or so. This will cause it to get hung up thinking, and sometimes it automatically changes the year to some distant future date like in the year 2507.
As well, selecting a Start time in the AM, and an End time in the PM such as 9AM-9PM causes the calendar to say "Events cannot end before they start."
To test: simply go to the Test calendar on the Show Instance and try creating a new event. Play with the Hours on the Start and End times by just changing them around several times. This will always result in the calendar lagging out and sometimes an unresponsive page.
I will replicate this in a tiki show instance.
Couldn't exactly reproduce as discussed in the comments but maybe r57822 might help?
|No attachments for this item|