Fri, 10 Apr 2026 04:38:50 +0000 https://bugs.horde.org/ticket/9880 Changing time of recurring events via drag/drop broken Using dynamic kronolith, editing the date or time of a recurring event by using drag/drop corrupts the recurring event data. This happens because the updateEvent call is made with the new times of the *current* instance of the recurring event, but the data stored for a recurring event should be the date/time of the original instance. Not sure the best way to handle this UI-wise. The choices I see are: (1) Automatically assume that the current instance should be edited, and add it as an exception. (2) Assume the entire series is being edited, and adjust the original entry (probably not the best idea, as this would probably NOT be what the user intended). (3) Disable drag/drop editing of recurring events. Thoughts? Tue, 12 Apr 2011 01:27:30 +0000 https://bugs.horde.org/ticket/9880#t63520 Bumping to medium since it can lead to loss of event data from the calendar. Tue, 12 Apr 2011 01:28:26 +0000 https://bugs.horde.org/ticket/9880#t63521 At first I considered 2) the correct choice. But 1) would probably be even smarter. Tue, 12 Apr 2011 09:22:20 +0000 https://bugs.horde.org/ticket/9880#t63532 After mulling over this while trying to sleep last night, I agree. I think automatically creating an exception would be the expectation here. Tue, 12 Apr 2011 14:47:47 +0000 https://bugs.horde.org/ticket/9880#t63546 Actually, 2) is what we already do. What issues do you see? This seems to work fine for me. Tue, 12 Apr 2011 16:55:15 +0000 https://bugs.horde.org/ticket/9880#t63553 > Actually, 2) is what we already do. What issues do you see? This > seems to work fine for me. This only works if editing the first event in the series. To repro: Create weekly recurring event Edit, for example, the third occurence byvdraggin the end time to later. This happens because we are keeping all the *original* event's data - like the original st time - and changing the part that changed...in this example, making the event span a week or more. Tue, 12 Apr 2011 18:16:35 +0000 https://bugs.horde.org/ticket/9880#t63566 Another example: Create weekly recurring event. Relocate one of the recurrences other than the first one by dragging it to a later time. This causes the entire series to disappear other then the one just edited. Tue, 12 Apr 2011 18:26:05 +0000 https://bugs.horde.org/ticket/9880#t63567 Sorry, that last example is rdproducable by adjusting the start and enter times separately, not by dragging the entire event. Tue, 12 Apr 2011 18:29:39 +0000 https://bugs.horde.org/ticket/9880#t63568 Changes have been made in Git for this ticket: Bug: 9880 Fix drag/drop editing of recurring events. If a recurring event occurence is moved or the time span is changed via drag/drop it is now automatically added as an exception to the recurring event. 2 files changed, 99 insertions(+), 17 deletions(-) http://git.horde.org/horde-git/-/commit/24e4771f380dabb49ade6d5eb31d4aebc2033083 Sat, 16 Apr 2011 00:30:32 +0000 https://bugs.horde.org/ticket/9880#t63819 This doesn't work with month views yet. Fri, 29 Apr 2011 15:48:36 +0000 https://bugs.horde.org/ticket/9880#t64298 Changes have been made in Git for this ticket: Bug: 9880 Fix creating exceptions by drag/drop in month view 1 files changed, 1 insertions(+), 1 deletions(-) http://git.horde.org/horde-git/-/commit/cea4c8db70730f6d7c8163a8c2eebdef46d5fe8c Fri, 06 May 2011 01:42:34 +0000 https://bugs.horde.org/ticket/9880#t64494