- This topic has 70 replies, 13 voices, and was last updated 13 years, 6 months ago by
.
-
Posts
-
Can you please let me know an ETA on fixing this issue. I cannot make any changes to recurring events. Instead of editing the event I have to delete all instances of the event and set it up again.
Hi Chad – we fully appreciate that this is less than ideal and we are working hard to fix it; unfortunately it is looking as if this a larger problem than at first anticipated.
For that reason the fix is unlikely to be available for the next monthly maintenance release and I’m afraid we can’t offer up a timetable for any releases beyond that.
From the sounds of things the temporary workaround I posted on Oct 18 isn’t working for you here? (It doesn’t anyway rectify the underlying problem, but in most cases it should allow you to edit affected events.)
“David, Webotools, Jeremy and anyone else experiencing this: have any of you experienced this same problem in a situation where the Hide from Upcoming Events List feature was not used? If so it would be great to hear about the circumstances so we can build a more complete picture of this.”
(I may be a little late to the party here, but:) We do not use the Hide from Upcoming Events List feature at all, as our upcoming events list in the sidebar widget only shows one particular category.
No worries Jeremy – yep the Hide from Upcoming Event List was something of a red herring here. This problem runs a little deeper and the devs are currently considering options to fix this.
Thanks for taking the time to post with your experiences, though, it definitely helps us.
Hi all. I just wanted to chime in here now that we’ve all discussed this internally, and cleared up a few points of confusion. There are two distinct issues at play here:
1. a BUG related to the javascript spinner; when you break an event out of a recurrence pattern, then try to update that broken-out event, the spinner loads infinitely and your save never actually goes through.
2. a FUNCTIONALITY ISSSUE (not a bug) related to how events are broken out of recurrence. Let’s say you have a recurring event that runs from today for the next 15 days; you go into the 3rd event in that series, change the description or title, and elect to apply that either to only this event (in which case it is broken out of the recurrence pattern) or all future events (in which case any events before this are broken out of the recurrence). This is intended behavior and is intended to be the same as how Google Calendar or iCal behave; if you change the details of an event, then those details aren’t consistent with the rest of the events in that series…and so they aren’t really all the same recurrence to begin with. Recurrence as it was built was the same specifics for all events in a pattern – if specifics change, that event isn’t technically part of the recurrence. It’s its own event.That being said, for #2, it seems obvious that this behavior isn’t necessarily what users want. Since we’re reengineering how recurrence works for 3.0, this is now a high priority aspect of that discussion…we want to give you guys the flexibility you need without breaking too much from industry standard. We’re also looking to get the issue of the infinite load worked out sooner, in an upcoming maintenance release, so you at least have the ability to update/modify those broken instances of the pattern as you need. All that to say that #1 will almost certainly come before #2.
Just wanted to make sure we’re all on the same page about this. We appreciate all of your feedback so far and it is adding significant value to our internal discussions on this. If anyone has other ideas or suggestions please do let us know.
Thanks for the clarification, Rob.. As far as I’m concerned, fix the bug, the functionality makes perfect sense to me! Maybe a note that alerts the user the events are disconnected would help clear up some of the confusion. I’m down with your “make it like google and ical” strategy. Sticking with standards is a good thing!
I am in complete agreement with fixing the javascript bug as the higher priority issue.
As far as #2, the functionality issue, I’d like to make these points:
1) Events may recur at irregular intervals. I might have an event scheduled for 7:30 PM tomorrow, and the identical event scheduled for 2:00 PM the following day. Or an event scheduled for Monday morning this week, and Thursday afternoon next week. To my mind, those are still recurring events.
The way TEC stands today, the only way I can configure TEC to allow these irregular recurrence patterns is to break an event out of its recurrence and save it for a different date or time. (Perhaps you have a better solution?)
It would be nice if TEC were able to deal with irregular recurring patterns like this. From an implementation perspective, you might consider allowing me to configure multiple dates and times when an event will occur, rather than (or in addition to) selecting a recurring pattern. [I’m envisioning an array of dates & times, rather than a recurrence pattern? Make sense?]
2) If an event recurs only a few times, I could achieve the same effect if I were able to duplicate the event within TEC, and assign the duplicated event to another date and time. (A third-party plugin can achieve this result today, but it is less than ideal.)
While that is not as elegant a solution as I described above, it would be a functional solution if an event recurs only a small number of times.
In any case, the functionality to “duplicate an event” within TEC would be useful, and I would like to see it included in the product.
- The topic ‘Cannot save certain recurring events’ is closed to new replies.