Ticket #219 (defect)
Opened 6 years ago
Last modified 5 years ago
adding recurring event reference to "my calendar" throws exception
Status: new
| Reported by: | johnsa | Assigned to: | douglm |
|---|---|---|---|
| Priority: | major | Milestone: | Bedework 4.0 |
| Component: | web clients | Version: | |
| Keywords: | Cc: | ||
User is prompted to specify calendar in the personal client; once we select and submit this step, we fail with:
Change History
04/09/07 13:08:25: Modified by johnsa
- description changed.
04/20/07 15:10:06: Modified by johnsa
- milestone changed from Bedework 3.3.1 to Bedework 3.3.2.
07/06/07 16:11:48: Modified by johnsa
- milestone changed from Bedework 3.3.2 to Bedework 3.4.
Milestone Bedework 3.3.2 deleted
09/25/07 10:42:29: Modified by douglm
- milestone changed from Bedework 3.4 to Bedework 3.5.
01/29/08 09:40:44: Modified by douglm
- milestone changed from Bedework 3.5 to Bedework 4.0.
Milestone Bedework 3.5 deleted
02/25/08 10:14:04: Modified by douglm
- description changed.
This is due to the way intances are handled, by the creation of a transient (for non overridden intances) annotation and associated proxy.
The event ref tries to point at that annotation.
To make this work is going to be difficult - we may require some sort of special instance ref.
What happens when say a non-overridden instance is overridden - we probably want to see that in the referring calendar

hidden the ability to add a recurring event instance; we will correct this by adding a master event or copying an instance