Possible recurring events bug

[gunnisen]

Hi!

Could you please see if you can reproduce this behavior:

1) I create a recurring event, e.g. repeat daily for the next five days (Mon-Fri this week).
2) I edit the Wednesday event, e.g. make it shorter.
3) I then go back to the first event (Mon) and double-click it to edit the title.
4) Now I have TWO events on Wednesday; the one I shortened in no. 2 and the recurring event w/edited title.

Is this the expected behavior?

Best regards,
  Gunnar

[Georgi Krustev]

Hello Gunnar,

 
I could not reproduce the issue on our online demos. Probably I am missing something.

Regards,
Georgi Krustev
Telerik

[Liz]

The video on the online demo did not follow the process the original complaint outlined. I am getting this same error, and I CAN reproduce it on the online demos.
Could someone please look into this following the directions suggested below exactly? There is a problem.

[Georgi Krustev]

Hello Liz,

 
I tried again to replica the issue following the steps exactly as Gunnar described them. Here is a screencast of my test. As you can see the Scheduler renders the recurring events correctly. Could you please point what I am missing? If you can send me a simple movie, which shows the required steps will be really helpful.

Regards,
Georgi Krustev
Telerik

[gunnisen]

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

[gunnisen]

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

[Georgi Krustev]

Hello again Gunnar,

Thank you for the screencast. When the whole series is updated, the Scheduler data source will try to remove all recurrence exception, at least will call the destroy Action method. Could you please verify that scheduler is actually trying to delete all recurrence exception? It will be very helpful if you can send us a simple test project, which replicates the issue in order to review the problem locally.
Looking forward to hearing from you.


Regards,
Georgi Krustev
Telerik

[gunnisen]

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

[Georgi Krustev]

Hi Gunnar,

 
Yes, when the end user decides to modify the whole series all exceptions will be deleted. This is done to assure that all exceptions related to old (before the modifications) are deleted. Thus you can be sure that there will be no orphan exceptions. Nevertheless, you are right that this process is hidden from the user's eyes.
Probably we will show a confirmation dialog, which will inform the user about the upcoming process. I will log it for further investigation.

Regards,
Georgi Krustev
Telerik

[gunnisen]

I would suggest letting the user choose whether or not to delete exceptions in this case. :-)

--Gunnar 

[Georgi Krustev]

Hello Gunnar,

 
The behavior, which I suggested is similar to how the Outlook works. Do you mind open a uservoice discussion on the same subject? Thus we will gather community feedback about this functionality.

Regards,
Georgi Krustev
Telerik

[gunnisen]

OK, done. :-)