#178 For Recurring Entries, don't overwrite the past

[Anonymous]

I'm not sure if this has been asked for before. Basically, as we go through the semester, we use MRBS to keep track of what happened. This works well enough for single events. However, when there is a recurring event, if we make changes to single occurrences, these are deleted if we need to update the whole series. For example: a class meets every Tuesday for the fall semester. Say there is a snow day on Nov. 8. We update the occurring for that day to have the title "Math 101: Cancelled - Snow day." Then, today, new information needs to be added to the description for the remainder of the class, so we edit the series and save it. Now the "...Snow day" is gone. It would be really great if there could be an option to save all of the past occurrences "as is" and then create a new series, based on the old series, with whatever new information.

So, when saving the series, a check box could say "keep old data?" (yes/no).
If yes, then the system would delete only future events, then create a new recurring entry with the new information.

If this suggestion sounds like a good addition to the MRBS feature set, I can work up some php code to assist.

-savigil

[Alex hanrahan]

This sounds like a great idea. I was hoping that a feature like this would be added. Perhaps even as a third option in the list: "edit event; edit event and future bookings;edit series."

Please, please introduce this feature!