.
.

Sunday, April 22, 2018

A bug in thousands of LDS.org links to scripture

[This discussion pertains only to browser based LDS.org and not to any version of the Gospel Library App.]

General Conference talks quote scripture. On LDS.org the scripture references are linked to the online standard works.


How it looks when it works

In this example, we will see how these links are supposed to work.

  1. Go to the main LDS.org menu.

  2. Select Scriptures and Study > Study Helps > Topical Guide.

  3. On the Topical Guide alphabet bar, click the letter G.

  4. Scroll down and select the topic "God, Foreknowledge of."

  5. Find the phrase "called … according to the foreknowledge of God."

  6. Click the link for Alma 13:3.


The screen will jump to chapter 13 of Alma. Verse 3 will be highlighted and centered vertically on the screen. This is the intended behavior.


How it looks when it doesn't work

Thousands of scripture links in General Conference talks jump to the correct chapter, but do not display the correct verse.

You can see this for yourself. Lookup President Russell M. Nelson's April 2018 Priesthood Meeting closing address. At the end of the talk, click "Show References." In footnote 12, click the link for Alma 13:3 (the same scripture verse we looked at previously).

This time you see the chapter heading for Alma 13 instead of verse 3.


So what exactly is the bug

To see the actual bug, we compare the two address bar contents:

a. Topical Guide link
a.    https://www.lds.org/scriptures/bofm/alma/13.3?lang=eng#p2
b.    https://www.lds.org/scriptures/bofm/alma/13.3?lang=eng#2
b. General Conference link

Notice the lower case "p" just before the "2" at the end of the Topical Guide link (the link that works).

Now go back to President Nelson's April 2018 General Priesthood Meeting talk and click on the footnote 12 link again. When you see the chapter heading, navigate to the browser address bar, manually add the missing lower case "p" just before the "2" and hit enter.

Voila.

LDStech: Now that you've seen this bug, could you please fix it?

0 Comments:

Post a Comment

<< Home