We have this same error message and it only affects one individual, who happens to be the Relief Society president. Others on the same computer/same browser can see the calendars just fine, but when she logs in on this or any other computer and clicks calendar she sees this error immediately before any of the calendars display. It started happening for her when she moved in from another ward where she had specific calendar editing rights. This issue has escalated from ward clerk to stake clerk and now needs to go higher. If indeed her account is "messed up" somehow, whom should we contact to have this fixed?
Temporarily not available
-
- New Member
- Posts: 10
- Joined: Sun Sep 11, 2011 6:42 pm
- Location: Provo, Utah, USA
-
- Community Moderators
- Posts: 11477
- Joined: Mon Mar 17, 2008 10:27 pm
- Location: US
Re: Temporarily not available
Make sure her membership record is actually in the ward.
Make sure she is entered in MLS in the standard position of RS President.
Check CDOL or at LDS.org/Directory under Leadership to see if she shows there as RSP.
Call Local Unit Support and explain the problem.
Make sure she is entered in MLS in the standard position of RS President.
Check CDOL or at LDS.org/Directory under Leadership to see if she shows there as RSP.
Call Local Unit Support and explain the problem.
- aebrown
- Community Administrator
- Posts: 15153
- Joined: Tue Nov 27, 2007 8:48 pm
- Location: Draper, Utah
Re: Temporarily not available
[Moderator note: These posts were split from the Temporarily not available topic in the Directory forum section. The issue at hand here deals with the Calendar application, which is an entirely different application.]
-
- New Member
- Posts: 10
- Joined: Sun Sep 11, 2011 6:42 pm
- Location: Provo, Utah, USA
Re: Temporarily not available
She's in CDOL as the RS president so I'll work with Local Unit Support.
-
- Member
- Posts: 162
- Joined: Sun Mar 04, 2012 11:34 am
- Location: South Jordan, UT, USA
Re: Temporarily not available
Curious to know if she shows up in the lds.org Directory as RS President...
We had some new/old High Councilors that were showing up in CDOL as they should and I assumed in MLS as well, since the Stake Clerk told me they were, though I didn't look for myself, plus I assumed if they were in CDOL, they must have been changed in MLS by the clerk and consequently uploaded to CDOL. However, they were not showing up in the lds.org directory or any of the other lds.org applications as such (i.e. permissions by calling for Hich Councilors were not being applied to them)
Several days later it was still not showing up in LDS.org and I had the stake clerk look at MLS again and sure enough they were not showing with the changes there. Had him re-do the changes, send/receive, and when we checked the next day everything was showing up correctly in all 3 places.
We had some new/old High Councilors that were showing up in CDOL as they should and I assumed in MLS as well, since the Stake Clerk told me they were, though I didn't look for myself, plus I assumed if they were in CDOL, they must have been changed in MLS by the clerk and consequently uploaded to CDOL. However, they were not showing up in the lds.org directory or any of the other lds.org applications as such (i.e. permissions by calling for Hich Councilors were not being applied to them)
Several days later it was still not showing up in LDS.org and I had the stake clerk look at MLS again and sure enough they were not showing with the changes there. Had him re-do the changes, send/receive, and when we checked the next day everything was showing up correctly in all 3 places.
-
- New Member
- Posts: 10
- Joined: Sun Sep 11, 2011 6:42 pm
- Location: Provo, Utah, USA
Re: Temporarily not available
She is in lds.org's Directory as RS president.
Local Unit Support directed me to have her use the lds.org's Feedback feature to solve the problem, since it is supposed to be "self-supporting", so we'll try that route and see what happens.
Local Unit Support directed me to have her use the lds.org's Feedback feature to solve the problem, since it is supposed to be "self-supporting", so we'll try that route and see what happens.