Clicking on lesson title and then returning and editing causes eternal spinner

eblood66 · Post by **eblood66** » Sun Feb 12, 2012 11:36 pm

In the administration view, if I click on the title of a lesson (to go to the lesson elsewhere on lds.org) and then return to the view and edit, I get an eternal spinner.

To reproduce:

Go to the Administration view
Select the Year View for a class
Click on a lesson link for a Class Manual lesson
Hit the back button
Click on the edit button for any lesson
The spinner shows up and the page never loads
If I reload the page it forces me to sign in to my LDS Account again

This is on Firefox 10.0.1 under Windows 7. Using Firebug it shows that when I click on the edit button it does a GET to https://www.lds.org/lesson/services/<my ... ssons/8235 which returns a 302 error. Immediately after that it shows a GET to https://www.lds.org/SSOSignIn/.

jdcr256 · Post by **jdcr256** » Mon Feb 13, 2012 11:05 am

Thanks for the report. The problem is that the chapter links are http. As soon as you visit a non-secure link, it kills your browser single-sign-on session for some reason. We'll probably end up switching all our manual/chapter links to use https.

ctbarrett · Post by **ctbarrett** » Tue Feb 14, 2012 10:18 pm

Same problem here with Chrome.

eblood66 wrote:In the administration view, if I click on the title of a lesson (to go to the lesson elsewhere on lds.org) and then return to the view and edit, I get an eternal spinner.

To reproduce:

Go to the Administration view

Select the Year View for a class

Click on a lesson link for a Class Manual lesson

Hit the back button

Click on the edit button for any lesson

The spinner shows up and the page never loads

If I reload the page it forces me to sign in to my LDS Account again
This is on Firefox 10.0.1 under Windows 7. Using Firebug it shows that when I click on the edit button it does a GET to https://www.lds.org/lesson/services/<my ... ssons/8235 which returns a 302 error. Immediately after that it shows a GET to https://www.lds.org/SSOSignIn/.

jdcr256 · Post by **jdcr256** » Wed Feb 15, 2012 10:22 am

Yep, this should happen in any browser, since the problem is in how LDS.Org handles authenticated sessions. It will be fixed when I next update the beta environment.