Page 1 of 1
Can not access ward list
Posted: Wed Nov 30, 2011 3:35 pm
by shspackman
I logged on to LDS.org today and can not access my ward list (households). I can access lists of all of the other wards in my stake. The leadership list works. My profile also. My wife's log in gives the same results. Any thoughts?
"
There were no search results found " This is the message that appears.
Other Ward members are having the same problem.
Posted: Sun Dec 04, 2011 7:37 pm
by shspackman
shspackman wrote:I logged on to LDS.org today and can not access my ward list (households). I can access lists of all of the other wards in my stake. The leadership list works. My profile also. My wife's log in gives the same results. Any thoughts?
"
There were no search results found " This is the message that appears.
Other Ward members are having the same problem.
Does anyone have a solution to this problem?
Posted: Sun Dec 04, 2011 7:44 pm
by aebrown
shspackman wrote:Does anyone have a solution to this problem?
It sounds like a problem that is unique to your ward. I really doubt that you can do anything on your own to correct it.
So I would suggest that you ask your ward clerk or some other leader to call Local Unit Support tomorrow.
Posted: Sun Jan 08, 2012 12:05 am
by craftyleo
We have the same problem and so do others in our ward, unfortunately we have no solution. Our clerk doesnt know how to solve it.
Posted: Sun Jan 08, 2012 2:22 am
by russellhltn
shspackman wrote:I logged on to LDS.org today and can not access my ward list (households). I can access lists of all of the other wards in my stake. The leadership list works. My profile also. My wife's log in gives the same results. Any thoughts?
I wonder if someone set all the profiles in your ward to "Private".
Posted: Sun Feb 12, 2012 10:47 am
by shspackman
Last Friday our problem was solved. Frank at Local Unit Support, Tier II: along with another Brother logged on remotely to my computer. Using Firefox andthe Firebug app, we looked at the line code. We were missing a ine of code dealing with our directory. They took a couple of screen shots for reference and within 24 hours we were up and running again.