The UI for defining event repetition is almost impossible to interpret.

I have used quite a bit, but I still have SERIOUS problems understanding how the advanced pattern cooworks with the rest.

I often end up with multiple copies of the same event on the same day, which means one have to delete all occurrences and start over.

The exception management simply does not work at all. Adding an exception have no visible or, AFAICS practical, effect.

I was adding an event that repeats from may to june, then again from august 12. through september. I failed tree times, and ended entering the event two times, one for spring and one for autumn. Lucky for me, there is no exceptions apart from the summer holiday.

These problems make the event repeat module close to unusable.

Comments

seanbfuller’s picture

seanbfuller commented

I actually agree. The interface would need a complete redesign to make it user-friendly. I think it was built with the intent that it would get an overhaul, but that never happened.

I haven't been able to figure out why the exceptions stopped working. In the next version I was planning on just removing them. You can just as easily browse through the calendar and delete the events you don't want, which is more like how iCal would have you do it.

anders’s picture

anders commented

I just created a calendar in google calendar today, and typed in about 50 events, 4 of which was repeated and had exceptions. It was extremely easy, though the slowest part was browsing the whole year to delete the exceptions (about 20 in total). What google calendar does that works so well is showing only the relevant controls based on the repeat type. This does of course require either reloading the page, or doing some hocus pocus with javascript. But it sure is nice ;)

rmiddle’s picture

rmiddle commented
Status: Active » Closed (duplicate)

UI needs work. This is know. Marking this a Duplicate.

Thanks
Robert