Tech Forum

I have been trying to add a Stake calendar and when I finish all of the options and hit save I get an eternal spinner. It does not go away. If I refresh the screen it clears it out and the calendar is not saved. Must be a broken link somewhere. Anyone else having the problem?

rgdlm wrote:Anyone else having the problem?

I just created a stake calendar with no problems at all, so it's not a universal problem.

I created both a private and a public calendar. It was interesting that the private calendar was created immediately (about 1 second) but for the public calendar I did get a spinner for perhaps 8-10 seconds before the calendar appeared in the list. So that limited test seems to indicate that it takes considerably longer to create a public calendar. But in any case, both calendars were created correctly.

I'm still getting the eternal spinner. Tried it from my PC, and from my iPad with the same result.

aebrown wrote:It was interesting that the private calendar was created immediately (about 1 second) but for the public calendar I did get a spinner for perhaps 8-10 seconds before the calendar appeared in the list.

Is email notification created for private calendars? I'm wondering if there's something wrong with rgdlm's stake that's causing that step to fail.

rgdlm, what happens if you create a private calendar (as a test)? You can try to make it public later.

Private calendar works fine. Set up within a second or two. Still getting the eternal spinner on Public.

rgdlm wrote:Private calendar works fine. Set up within a second or two. Still getting the eternal spinner on Public.

As a possible workaround, you might try creating a private calendar, saving it, and then changing it to a public calendar. I suppose there's some chance that might work, even though creating a public calendar directly doesn't seem to.

I tried the work around you suggested and it worked. Problem with creating it directly not solved but this will give me the ability to help our building scheduler with her calling. Thanks

Just confirming that I had this same issue and that the workaround also worked for me.