Wrong ward/stake when logging in to Beta Directory

When I log into the Beta directory (https://lds.org/rcdirectory), the ward/stake listed is in California (Menifee). I'm in a YSA ward in Salt Lake City, UT. When I log into the current production site (https://lds.org/directory), my ward/stake is correct. Is there something wrong with my account in the beta environment, or does everyone else see what I'm seeing? I'd like to test this in my ward/stake, as I'm the website administrator for my ward.

Thanks!

wertdl wrote:Is there something wrong with my account in the beta environment, or does everyone else see what I'm seeing?

I'm not seeing that problem -- the beta directory takes me to my correct ward and stake.

wertdl wrote:When I log into the Beta directory (https://lds.org/rcdirectory), the ward/stake listed is in California (Menifee). I'm in a YSA ward in Salt Lake City, UT.

Where you in that ward recently? Some of the past betas have used a data set that's a few weeks/months old.

russellhltn wrote:

wertdl wrote:When I log into the Beta directory (https://lds.org/rcdirectory), the ward/stake listed is in California (Menifee). I'm in a YSA ward in Salt Lake City, UT.

Where you in that ward recently? Some of the past betas have used a data set that's a few weeks/months old.

Nope. I don't even know where Menifee, CA is.

Confirming. I see the Canyon Lake Ward in the Menifee California Stake when I enter https://lds.org/rcdirectory. If I enter https://lds.org/directory, I see my correct ward and stake.

I also get the stake in California when I click on that link. Is that a real stake? Am I seeing real information about those people? Seems like a major privacy issue.

mrrad wrote:I also get the stake in California when I click on that link. Is that a real stake? Am I seeing real information about those people? Seems like a major privacy issue.

Yes, it's a real stake (it's located in the southwest portion of Riverside County, California -- east of Orange County).

It's interesting that some people seem to get directed to that particular ward/stake, but others (I, for example) properly go to their own ward/stake.

And it does seem like a privacy issue that needs to get fixed ASAP.

Same problem here. I live in Washington State but the beta directory lists me in a stake from North Carolina.

I'm getting the Rupert 7th Ward in Rupert, ID. I do know where Rupert is, but have never lived there.

I thought there might be some sort of relationship of Unit numbers, but I can't figure it out.

mfmohlma wrote:I'm getting the Rupert 7th Ward in Rupert, ID. I do know where Rupert is, but have never lived there.

I also default into the Rupert 7th Ward, I cant see any of the Ward info except for the Missionary info but not the Ward Mission Leader's, When I go into the Stake I can see the Stake Activities and Sports, Stake Stake Presidency, and Stake Relief Society Presidency.

If I click on any other Stake calling set it reloads or if I try to go to any other Ward it reload back to the Rupert 7th Ward.

Side not when I first logged in I went to one of the Hawaii Stake and when I clicked on something I then went to the Rupert 7th Ward, also all the calling in the Stake are alphabetical, and every one I can see only have the 7 digit phone number not the 10 digit phone numbers except the Stake Presidency Second Counselor

Browser Firefox Nightly X64 Ver 21.0a1 (2013-01-09)

Yeah, I live in the Naperville Illinois stake, and sometimes I get the Orem Utah Hillcrest Stake, Hillcrest 3rd Ward, and other times I get Rupert Idaho Stake, Rupert 7th Ward. However, I'm not able to view the membership information for anyone in these units. Clicking on "Ward Leaders" or "Stake Information" from the dropdown causes the page to refresh, taking me back to "My Household."

We have tracked this down to a problem with data being cached in our system. When you see an incorrect stake/ward info you are seeing the info of someone that logged in prior to you. We have identified where this is happening and we are actively working to get it resolved as soon as possible.

This should be fixed. See Latest Patch 1/18/2013.