contao/test — Issue #1014: Calendar Duplicating Events in upgrade v2.7.2 to v2.7.3
Author: importer
Created: 2011-11-29 07:12:39+00:00
State: open
Labels: calendar, Defect

NOTE: I've tried to test this in the online demo, and the online demo FAILS when you try to create a new event. The last events shown are from 2007 and the demo displays a red error message when creating a current event. I have to assume that the bug described below exists in the online demo for v2.7.3.

I have two websites with TypoLight and we just upgraded in the last 48 hours from v2.7.2 to v2.7.3. No problems with the upgrades, but I'm seeing the same behavior in both installations.

If you create a new event in the Events area, regardless of one day or two day event, in both situations the event appears twice. If you create a single event, beginning Sep 21 09, and ending Sep 21 09, the event appears in the Calendar display on both Sep 21 and Sep 22. This also occurs if the ending date is left blank.

If you create a two day event, spanning Sep 24 and Sep 25, the event appears on Sep 24 and 25, and then again on Sep 26 and 27. I suspect this is a fairly serious bug in the 2.7.3 upgrade, and it seems to be reproducible in two separate installs with similar upgrades.

Any help would be appreciated as my client wants me to get this fixed FAST.

Leo:

Here's some additional information to help run this down. If I specify a Start and End time in a one day the event, the event does NOT duplicate.

If the Start and End Time are left blank, and we assume that this is a one day event, when I look in the MySQL Calendar Events table it appears that v2.7.3 populates the "Start" Time with the current DTG, and populates the "End" time with a DTG that is 23 hours, 59 minutes later. This may be a key to why everything is doubling up.

When I check the box to specify a start and end time, of course the time hacks run from 0:00 to 23:59.

So it appears that IF the "specify start and end time" box is UNCHECKED, the calendar in v2.7.3 is duplicating the creation time of the record for the event, populating the "start" time with the creation time, and then populating the "end" time with the creation time PLUS 23:59.

I can clear the error in the SQL database if I simply populate the end time with event start time, and then the calendar display of the event is correct.

Hope this is helpful, I would really like to get a solution to this quickly. Right now I would have to say that if anyone is using the calendar functions in TypoLight, they probably should NOT upgrade to v2.7.3 with this bug present.

If you come up with a "patch" for this, let me know so that I can apply the patch in advance of the fix if one is issued.

Ernest McDermon
Front Wave Websites
Snellville, GA
Home Office: 770-558-2973

[Download the attachments](http://www.contao.org/tl_files/tickets/1014.zip "Download the attachments of this ticket")

--- _Originally created by ernest on September 19th, 2009, at 03:12pm (ID 1014)_