{"issue":{"created_at":"2011-11-28T17:51:27Z","state":"open","updated_at":"2011-11-28T17:51:42Z","user":{"gravatar_id":"256406243346b9253f8610fb1d1e05f6","id":1215373,"url":"https://api.github.com/users/importer","avatar_url":"https://secure.gravatar.com/avatar/256406243346b9253f8610fb1d1e05f6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"importer"},"comments":11,"body":"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.\n\nI 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.\n\nIf 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.\n\nIf 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.\n\nAny help would be appreciated as my client wants me to get this fixed FAST.\n\nLeo:\n\nHere'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.\n\nIf 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.\n\nWhen I check the box to specify a start and end time, of course the time hacks run from 0:00 to 23:59.\n\nSo 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.\n\nI 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.\n\nHope 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.\n\nIf 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.\n\nErnest McDermon\nFront Wave Websites\nSnellville, GA\nHome Office:  770-558-2973\n\n[Download the attachments](http://www.contao.org/tl_files/tickets/1014.zip \"Download the attachments of this ticket\")\n\n--- _Originally created by ernest on September 19th, 2009, at 03:12pm (ID 1014)_","assignee":null,"id":2371113,"labels":[{"name":"calendar","color":"e6e6e6","url":"https://api.github.com/repos/contao/test/labels/calendar"},{"name":"Defect","color":"bd2c00","url":"https://api.github.com/repos/contao/test/labels/Defect"}],"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"number":1014,"title":"Calendar Duplicating Events in upgrade v2.7.2 to v2.7.3","html_url":"https://github.com/contao/test/issues/1014","closed_at":null,"url":"https://api.github.com/repos/contao/test/issues/1014","milestone":null},"action":"created","comment":{"created_at":"2011-11-28T17:51:42Z","updated_at":"2011-11-28T17:51:42Z","user":{"gravatar_id":"256406243346b9253f8610fb1d1e05f6","id":1215373,"url":"https://api.github.com/users/importer","avatar_url":"https://secure.gravatar.com/avatar/256406243346b9253f8610fb1d1e05f6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"importer"},"body":"Good morning Leo\n\n![](\n\nNo, we don't use \"unofficial\" patches. Only official Contao releases for me) :-)\n\nJust to confirm, I went ahead and downloaded another copy of the Contao core v2.9.5 from the Contao website and unzipped the files. The code I reported last night IS in the system/modules/calendar/Calendar.php file dated 3/2/2011 1:03pm at lines 399 - 441. In this case I was performing an upgrade from 2.9.3 (the error did NOT appear there) to 2.9.5 when this issue immediately occurred with my client updating their elementary school calendar. Not sure if it is also in 2.9.4.\n\nI assume this is some \"crud\" that has somehow crawled back into the core distribution. I'm not testing the v2.10.0 RC but you might check to see if this issue is also appearing in the Calendar.php file there as well. \n\nThe patch that was identified two years still works, is that the way to proceed?  I've updated a number of our sites to 2.9.5 and can easily patch this file, but it would be helpful in the next release if this can be fixed again.\n\nBTW, thanks for the wonderful Contao system and your excellent support! Our clients are really pleased with the benefits that your system offers them. I'm looking forward to the upcoming release of 2.10.\n\nErnest McDermon\nSnellville, GA\n\n--- _Originally created by ernest on July 29th, 2011, at 02:02pm_","id":2903956,"url":"https://api.github.com/repos/contao/test/issues/comments/2903956"}}