Bug: Bible dropdowns stop working after the first word

In the search pane, if I type in "glory", then add Jn 1:14, no Bible dropdown datatype is offered. To get the Bible dropdown, I need to first type in the Bible verse.

The same happens if I put in a Bible verse, select it, then try to add a second Bible verse.

Find more posts tagged with

Comments

Philana R. Crouch

Fr. Devin,

If you construct your search as:

glory <Jn 1:14> as soon as you type the reference it should start to populate. It's the same with your second example. I'll write up a case for the team to look at so they can determine if search should continue to require that <Jn 1:14> be used.

Fr Devin Roza

https://community.logos.com/discussion/comment/879744#Comment_879744

Thanks, Philana. I was aware that, after the first Bible reference, if I type a < and then the Bible reference, the dropdown still works. I find it frustrating, however, that the dropdown interface works in such a unpredictable fashion, at times requiring it and other times not.

So, writing John 1:14 at the beginning of the search box, without carrot brackets, correctly suggests the Bible datatype, transforming it into <John 1:14> when you select it. Then you have other situations where it also work properly, like when you write:

glory WITHIN {Milestone John 1:14

This also provides a dropdown for the Bible datatype John 1:14, that the user can select and have the text transformed to <John 1:14>.

My hope would be that the search tab dropdowns could be more consistent in their behavior, and that anytime you write a Bible verse you get the Bible datatype dropdown as an option.

Offering this type of functionality is particularly important because typing <> and {} is quite difficult on many foreign language keyboards.

NB.Mick

https://community.logos.com/discussion/comment/879754#Comment_879754

Offering this type of functionality is particularly important because typing <> and {} is quite difficult on many foreign language keyboards.

...not to mention that it is rather un-intuitive and complex, so most users won't remember using such syntax even on English language keyboards...