Tech Forum

I was the first to report this problem, but cannot find my original thread ... sorry.
I have cleaned up most of the errors, but I will need someone to please delete the following events. These were previously modified events in a repeating event series, which were reactivated during the migration to V2. This is causing wide-spread consternation and confusion.

When I attempt to delete them, I either get the eternal spinner, or the following message: "Sorry, data is temporarily not available for this application. Please try again later."
https://lds.org/church-calendar/event.j ... Id=2945683 (General Conference, 1,2 Sept, 2012)
https://lds.org/church-calendar/event.j ... Id=2687967 (Bishop Storehouse (Bumby), 4 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2687972 (Bishop Storehouse (Bumby), 5 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2687987 (Bishop Storehouse (Bumby), 8 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2687992 (Bishop Storehouse (Bumby), 10 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2687996 (Bishop Storehouse (Bumby), 11 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688001 (Bishop Storehouse (Bumby), 12 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688006 (Bishop Storehouse (Bumby), 15 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688008 (Bishop Storehouse (Bumby), 16 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688011 (Bishop Storehouse (Bumby), 17 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688015 (Bishop Storehouse (Bumby), 18 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688019 (Bishop Storehouse (Bumby), 19 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688024 (Bishop Storehouse (Bumby), 21 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688026 (Bishop Storehouse (Bumby), 22 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688028 (Bishop Storehouse (Bumby), 23 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2688031 (Bishop Storehouse (Bumby), 29 Nov, 2011)
https://lds.org/church-calendar/event.j ... Id=2691397 (Stake Mission Correlation / Bishop Training, 2 Feb, 2011)
https://lds.org/church-calendar/event.j ... Id=2691413 (Stake Mission Correlation / Bishop Training, 3 May, 2011)
https://lds.org/church-calendar/event.j ... Id=2691420 (Stake Bishops' Welfare Council, 5 July, 2011)
https://lds.org/church-calendar/event.j ... Id=2691427 (Stake Mission Correlation / Bishop Training, 2 Aug, 2011)
https://lds.org/church-calendar/event.j ... Id=2689102 (Stake Bishops' Welfare Council, 4 Oct, 2011)
https://lds.org/church-calendar/event.j ... Id=2691443 (Stake Mission Correlation / Bishop Training, 1 Nov, 2011)

Thank you

Did you try deleting by right clicking in the month view and delete? This has worked for mine.

I cannot do anything with any repeating event that moved over from V1 to V2. Right click or left click or any other click. I get the spinning wheel, then three blank lines on a screen that I support is supposed to have the event information for me to edit.

I cannot edit. I cannot delete.

I also cannot add a new event in the week view. Same screen appears with nothing in it.

KenRichins: Thank you for your response. I was able to clear up some migration problems prior to starting this thread. However, for the events which I listed above, neither the "right click" in calendar view, nor the "Delete" button in Edit session work. The "right click" produces a pop-up with the message I listed above, and "Delete" in Edit produces the eternal spinner.

I also cannot edit the events (to change the title to ".", for instance, to eliminate confusion in the calendar), nor can I change them to "non-repeating".

Thanks for all the detailed information several of you provided to help us track this down. It appears that there were several series of repeating events that did not get converted to 2.0 correctly. Whether it was due to a v1 bug that corrupted the data, or a bug in our conversion process, we do not know. Luckily, only 50 or so series were affected (out of the many thousands of total series).

We are experimenting with a method to clean up this data. However, our clean-up could have minor, unintended consequences. We are basically guessing which recurrence pattern was used when the event was created, so if a user opens the newly regenerated event and saves it, it could create new instances of the event if our guessed pattern is slightly off.

We are intending to contact the creators of the events via email before we modify their events.

As far as I am concerned, if you can delete the events listed in the first post of this thread, and following, I can clean up everything else.

The following events also need to be deleted:

https://lds.org/church-calendar/event.j ... Id=2945954 (Evening Adult Session, 6 October, 2012)

https://lds.org/church-calendar/event.jsp?retPage=index.jsp&eventId=2945950 (Evening Adult Session, 7 April, 2012)

https://lds.org/church-calendar/event.j ... Id=2945683 (title: (deleted), 1 Sept, 2012)

Thank you

I am getting the same problem. I tried the right clicking thing and still get the error and can not delete the events that are corrupted.

I appreciate your work on resolving this issue. However, it is getting critical on our side. Today is the first day we are distributing calendars for November and December to Priesthood Executive Committees, and we have eleven (11) events on our November calendar which need to be deleted / modified.

Thank you for prioritizing this serious problem.

Chuck Olsen, Orlando Florida South Stake Executive Secretary

I just noticed this today. In my case, what I am seeing is that for those recurring events for which I made exceptions to specific instances, after the conversion to 2.0 the exceptions show up as separate stand alone events, and the original series shows up complete without any exceptions. So for example, stake pec was set for 1st and 3rd thursdays at 7:30. then on a specifi day (jan 19 happens to be stake council) PEC was changed to start at 8:30. After the conversion, there are two pec events on that day of stake council...a 7:30 instance (part of the series) and a new standalone instance starting at 8:30.

to jdcr256: Is this part of the 50 affected series you mention above, or is this a different issue? This is for the Kansas City Missouri Stake, 'STK - Core Planning Calendar'. I haven't studied other series with exceptions...I was assuming that all of them would have been treated the same.

Thank you.

ross.rick wrote:In my case, what I am seeing is that for those recurring events for which I made exceptions to specific instances, after the conversion to 2.0 the exceptions show up as separate stand alone events, and the original series shows up complete without any exceptions.
...
Is this part of the 50 affected series you mention above, or is this a different issue?

I'm pretty sure that everyone experienced the particular problem you mentioned with exceptions to repeating events. I know that my stake alone had at least a dozen such series. I find it hard to believe that our stake accounted for 25% of all such problematic series. So either jdcr256 wildly underestimated this problem, or he was talking about a different problem.