Tech Forum Archive

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

4 postsstarted by eblood66 2,214 viewsoriginal topic

eblood66
Senior Member
#1
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:
  1. Go to the Administration view
  2. Select the Year View for a class
  3. Click on a lesson link for a Class Manual lesson
  4. Hit the back button
  5. Click on the edit button for any lesson
  6. The spinner shows up and the page never loads
  7. 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
Church Employee
#2
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
New Member
#3
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:
  1. Go to the Administration view
  2. Select the Year View for a class
  3. Click on a lesson link for a Class Manual lesson
  4. Hit the back button
  5. Click on the edit button for any lesson
  6. The spinner shows up and the page never loads
  7. 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
Church Employee
#4
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.