Page 2 of 2

Re: Formatting url to search for specific verses

Posted: Wed Dec 13, 2017 6:20 pm
by corwinslack
Here is the answer

Https://www.lds.org/scriptures/search?l ... 20-22%2C24

The spaces in the string 1 Cor 1:20-22,24 need to be replaced with +. The colon needs to be replaced with %3A. And the comma needs to be replaced with %2C

- (dash) apparently does not need to be replaced.

Thanks for the nudge. It helped me go the right direction. The Inspector in Google Chrome is fantastic. I wish I understood 1% of it.

Re: Formatting url to search for specific verses

Posted: Wed Dec 13, 2017 6:22 pm
by corwinslack
Here is what comes after the ?

lang=eng&query=1+Cor+1%3A20-22%2C24

Re: Formatting url to search for specific verses

Posted: Wed Dec 13, 2017 6:26 pm
by corwinslack
This seems to work as well but I need to test it.

lang=eng&query=1%20Cor%201:20-21,24

Re: Formatting url to search for specific verses

Posted: Wed Dec 13, 2017 6:33 pm
by corwinslack
Tested and will continue to test. A lot of encode url encode methods will return the second version if 1 Cor 1:20-21,24 is entered.

(Sorry about the inconsistency over verse 22 and 22. It is not significant).

Re: Formatting url to search for specific verses

Posted: Mon Nov 04, 2019 8:56 am
by banfordm
When I click on

https://www.lds.org/scriptures/nt/1-cor ... ng=eng#p21

my web browser changes the address to

https://www.churchofjesuschrist.org/stu ... 1?lang=eng,

which eliminates the blue bar marking specific scriptures and the scroll feature. If I try and manually type in the "verse=21-25" and then proceed my browser corrects it to the latter link. How do I stop my browser from changing the link?

Re: Formatting url to search for specific verses

Posted: Mon Nov 04, 2019 10:38 am
by sbradshaw
This looks like a bug – I'd recommend sending it as feedback. There is a newer format for URLs – this is what the Gospel Library app outputs when sharing:
https://www.churchofjesuschrist.org/study/scriptures/nt/1-cor/1?id=p21-p25&lang=eng#p21
but that doesn't work either (it still redirects).