Frequent issues with logging in and out on lds.org

I searched for an answer to my issue in this forum and failed to locate an answer, so I apologize if I missed it.

I have my notes/journal bookmarked and open it daily to do my scripture study. I'm baffled to note that, almost every day, when I log into my notes/journal, my login status is not signed in (I know because I see "sign in/tools" at the top of the page). From there, when I click on my bookmarked scripture, I am taken to the sign in page. I'm largely okay with this because I have auto-login enabled with lastpass.

However, I'm thinking this must be a bug, and I would be really annoyed if I were typing in my username/password every time.

At any rate, how can I possibly log in to my own notes/journal, which are tied specifically to my account, and then be effectively not signed in (for purposes of navigating to other pages from the notes/journal)?

As an additional note, a similar behavior often occurs where I'm taking notes on a certain scripture page and, suddenly, my notes/annotations will fail to save, unless I log out and then log back in.

I forget if this has happened in a browser other than Chrome and would be willing to test if asked.

Thanks.

Browser: Chrome 32.0.1700.107 m
OS: Windows Version 6.1 (Build 7601: Service Pack 1) [Windows 7]
What other system information would help?

For example, the second issue I listed above (log in/out problems on scriptures.lds.org) is occuring, as I write this.

I had started in notes/journal, somehow not being signed in. I then clicked on my bookmarked scripture in Alma 32. This took me to a sign in page and lastpass automatically logged me in. From there I did reading. When I went to update my bookmark and clicked save, the message says "Saving" and the status indicator keeps spinning, and spinning, and spinning . . .

Okay, in fairness, after waiting a couple minutes for the spinning to stop, I clicked out of the box, did some other things for a couple minutes, tried the edit bookmark button, again, and it worked.

However, I'm still confused about the first attempt, where the indicator kept spinning and spinning.

This sounds like the issue where you get signed out from LDS.org if you ever access other LDS.org pages using HTTP (instead of HTTPS). It's easy for that to happen if you are using HTTP bookmarks or navigate some other way to scriptures using HTTP.

aebrown wrote:This sounds like the issue where you get signed out from LDS.org if you ever access other LDS.org pages using HTTP (instead of HTTPS). It's easy for that to happen if you are using HTTP bookmarks or navigate some other way to scriptures using HTTP.

Hmm. My notes/journal is https and the bookmarked scripture is https.

However, I do have open conference music (http), Google Docs, and the notes/journal (https), when I first start.

Maybe the conference music is the culprit and the solution would be to open it after opening the https notes/journal. What do you think?

Thanks for your reply! (I'll be offline, until later tonight/tomorrow, by thew way.)

fletch74 wrote:However, I do have open conference music (http), Google Docs, and the notes/journal (https), when I first start.

Maybe the conference music is the culprit and the solution would be to open it after opening the https notes/journal. What do you think?

It makes no difference whether you open conference music before or after you sign in. Any activity you do on LDS.org using HTTP after sign in will cause the problem. I'm assuming that within the conference music area you are following links as you work on your notes/journal, and that will trigger the problem if you are using HTTP in that area.

The solution is to make sure you open your conference music using HTTPS. Once you've done that, any links you follow within the conference music area should stay within HTTPS and you'll avoid the problem.

It may not be the http/https problem. I've experienced several problems like this on lds.org in the last several weeks. See my post: Staying "logged in". You might be experiencing something similar.

Thanks, guys.

I've tried the https/http technique, and from what I've seen, so far, it's working. Hurray!

I'll let you know if anything changes.