This is a migrated thread and some comments may be shown as answers.

Possible recurring events bug

11 Answers 180 Views

Scheduler

This is a migrated thread and some comments may be shown as answers.

11 Answers, 1 is accepted

answered on 28 Oct 2013, 10:42 AM

Hello again!

Here is a video showing what happens both in my GUI and in the database. As you can see, I seem to be losing the RecurrenceException when I edit the series (after first editing the single occurrence to lengthen it). If I set a breakpoint on the update method (I'm using ajax), I'm getting NULL for the RecurrenceException in this case. It's probably something I'm doing wrong, but I cannot seem to find the bug. Any suggestions where I might look?

Also, note that when I edit the single occurrence to lengthen it, I'm not getting the "broken circular arrow" icon showing that this is indeed a recurrence exception. However, at that stage, I DO have a value for Recurrence Exception in the database (that is only nulled when I edit the series title in the next step). Any idea why the icon is not appearing?

Another thing: In your screencast, when you edit the series after first changing the single occurrence, I notice that the edit you made to the single occurrence is lost (all occurrences are the same again). Is that expected behavior? I would think that the first edit was still valid and should be kept as is, even if you later make a change to the series (i.e. the recurrence exception should still be honored)?

All the best,
Gunnar

answered on 28 Oct 2013, 11:47 AM

Replying to my own post here... :-)

Turns out I had the following defined on my Datasource:
.Events(e => e.Sync(@<text>
function() {
this.read();
}
</text>))
This is something I found online and incorporated in order to make sure the scheduler did a read operation immediately when something was changed (I need that behavior in connection with some overlap handling I'm doing). Anyway, if I remove that snippet from my scheduler datasource definition, I'm getting the same behavior as you do in your screencast, Georgi.

What I don't understand is WHY that Sync handler should result in the double booking I showed in the video in my previous post. Any ideas?

ALSO: Even if I remove the Sync handler and get the same behavior you're getting, I am still not happy with losing the recurrence exception when editing e.g. the series title. Let's say I'm booking a room for five consecutive days for a course. It then turns out that on Tuesday, we need to start one hour later, so I edit that single occurrence. Then, perhaps I discover a spelling error in the course title or something. I edit the series to correct that, and boom, the Tuesday schedule change is gone. Not good. :-)

Best regards,
Gunnar

answered on 30 Oct 2013, 01:59 PM

Hi Georgi,

The double booking problem I described is probably due to some obscure bug in my code, so I won't bother you with that anymore. ;-)

Basically, what I'm now questioning, is the behavior that's also shown in your screencast (and is also easy to reproduce in the online demos), i.e. that if you have a series, then edit one single occurrence, and then later edit the whole series, the edit you made to the single occurrence is lost.

Let's say you've booked a room from 10 - 12 every Tuesday for the next year, then edit a single occurrence maybe two months ahead, and then later need to perhaps correct a spelling error in the series title. The edit you made to the single occurrence would then be lost, and that's not so easily spotted...

All the best,
Gunnar