Page 2 of 4

Posted: Sun Aug 19, 2012 1:59 pm
by Mikerowaved
Moderator note: This thread was moved from the LDS.org Website/Calendar forum to the LDS.org Website forum, as it applies to many more areas of lds.org than just the Calendar.

Posted: Sun Aug 19, 2012 3:00 pm
by ebastow
This is doing this to everyone in our Stake Leadership (I'm assuming USA wide)

Posted: Wed Aug 22, 2012 11:32 am
by kennova
Glad to see the issue is getting attention, it's still happening to our entire bishopric. Hopefully a fix is forthcoming.

Posted: Wed Aug 22, 2012 12:47 pm
by russellhltn
The quick fix is don't log out. I have IE set up such that each window is in a different session. Once I close the window, that's it - I'm out.

Posted: Wed Aug 22, 2012 2:38 pm
by aebrown
RussellHltn wrote:The quick fix is don't log out. I have IE set up such that each window is in a different session. Once I close the window, that's it - I'm out.


Agreed. I never sign out, unless I'm using a shared computer. That does happen when I'm on the clerk computer at church, but I close the browser completely when I'm done, too, so this language issue is not a problem for me at all.

Posted: Sat Sep 01, 2012 6:46 pm
by kennova
It signs me out automatically. Whenever it is idle for a time it signs me out. Even then, if I don't sign put explicitly (and actually I've never signed out explicitly), but just close the browser, the next time I go to lds.org it's set to Spanish.

Posted: Sun Sep 09, 2012 8:51 am
by kennova
Now it's choosing Korean for me... And the HP Group Leader is getting spanish as well. I see that the login form was updated, was this not fixed?

Posted: Sun Sep 09, 2012 9:02 am
by lajackson
kennova wrote:Now it's choosing Korean for me... And the HP Group Leader is getting spanish as well. I see that the login form was updated, was this not fixed?


They are very aware of the problem and are still working on it.

There are other threads on the subject, including these:


Posted: Sun Sep 09, 2012 10:02 am
by barkeraj
We know the cause and are working to get it fixed right now. Should be fixed any time now.

I can't go into the details, but this may pop up again over the weeks as we continue to work through the issue. Your reporting of it is very helpful, please continue to do so in the future.

Posted: Mon Sep 10, 2012 8:48 am
by kennova
Thanks Aaron and lajackson for the update.