BUG: 'Add Versions' Drop-down blank (Logos Pro)

I am running Logos 36.1.6 with a Logos Pro subscription on Windows 11. The Add Versions drop-down in the Bible Search window is blank when I click on it. There are no options to select. There's just a find box but the find box doesn't find any versions when you type something in.

I think this might be an issue with Logos Pro. I already had v36.1 prior to subscribing and I don't remember having this problem. I had recently used the drop-down and was able to select a version fine.

EDIT: This is not just a Logos Pro issue. I was able to duplicate the issue in my test account. It seems to be the search itself. Since it didn't return results in my top bible, I went to Fuzzy bible search, which gives results. But I still should be able to select another version to see the verses in a comparison translation. This still seems like a bug.

Find more posts tagged with

Desktop App

Comments

MJ. Smith

Does the problem occur only on Fuzzy searches? If so, it is likely intentional as the search criteria may not be met by other translations.

Kiyah

https://community.logos.com/discussion/comment/1317507#Comment_1317507

Does the problem occur only on Fuzzy searches? If so, it is likely intentional as the search criteria may not be met by other translations.

If it's intentional it's bad design. The whole point of going to Fuzzy search was because the search didn't return results for the precise wording. Fuzzy search did return results, so I should be able to compare versions for the results I got. Fuzzy search shouldn't be limited by whether or not Passage search returned results. That would completely defeat the purpose of having Fuzzy search in the first place.

It would be helpful if someone from Logos could chime in on whether this is intentional design. If so, it needs to be changed.

MJ. Smith

https://community.logos.com/discussion/comment/1317645#Comment_1317645

If so, it needs to be changed.

I would not want it to be changed. In a fuzzy search, I want each translation to stand on its own as often the reason I have resorted to a fuzzy search is because what I remember it outside my current top translations. However, if it were changed I could and would simply ignore the feature in that context.

Kiyah

https://community.logos.com/discussion/comment/1317668#Comment_1317668

However, if it were changed I could and would simply ignore the feature in that context.

This would be easiest. I think most users just want the software to work consistently. If I have results, I should be able to add a comparison version. It's not intuitive to the average user to not be able to add a version in this scenario. It gives the impression of a bug. I'm a nine-year user of Logos and this was confusing to me. Logos is supposed to be trying to make things easier for new users.

MJ. Smith

https://community.logos.com/discussion/comment/1317675#Comment_1317675

Logos is supposed to be trying to make things easier for new users.

I strongly support this. However, I am also concerned about the gullibility of the Logos/Verbum users accepting non-sensible information solely because Logos said it.

Kiyah

https://community.logos.com/discussion/comment/1317679#Comment_1317679

Logos is supposed to be trying to make things easier for new users.

I strongly support this. However, I am also concerned about the gullibility of the Logos/Verbum users accepting non-sensible information solely because Logos said it.

I don't understand what that has to do with adding a bible version to a view. I was just looking for the verse where Jesus said "the kingdom of God is in you" and wanted to be able to compare wording across translations. Since I didn't have the precise wording I didn't get a result and so I went to Fuzzy search. But now that I have results I still want the same functionality, I want to add a version to the view to check the wording.

What would be non-sensible about that information? Can you give an example of why not being able to add a bible version in Fuzzy bible search when you didn't get a result in your passage search would be a good thing? I'm just trying to understand your issue with making a change here.

Dave Hooton

I am running Logos 36.1.6 with a Logos Pro subscription on Windows 11. The Add Versions drop-down in the Bible Search window is blank when I click on it. There are no options to select.

I had options to select ESV and NABRE, also on v36.1.6 Pro:

Kiyah

https://community.logos.com/discussion/comment/1317733#Comment_1317733

I am running Logos 36.1.6 with a Logos Pro subscription on Windows 11. The Add Versions drop-down in the Bible Search window is blank when I click on it. There are no options to select.

I had options to select ESV and NABRE, also on v36.1.6 Pro:

Do you get options when you put in my search: "kingdom of God is in you"?

Dave Hooton

https://community.logos.com/discussion/comment/1317753#Comment_1317753

Do you get options when you put in my search: "kingdom of God is in you"?

Good one! There were no options for that term, but it used the versions I had previously chosen.

However, if the quotes are removed the Add version options are available.

Jonathan Bradley

https://community.logos.com/discussion/comment/1317675#Comment_1317675

However, if it were changed I could and would simply ignore the feature in that context.

This would be easiest. I think most users just want the software to work consistently. If I have results, I should be able to add a comparison version. It's not intuitive to the average user to not be able to add a version in this scenario. It gives the impression of a bug. I'm a nine-year user of Logos and this was confusing to me. Logos is supposed to be trying to make things easier for new users.

I don't know if anyone said this. I was having the same problem. I switched to a different search outside of Fuzzy Search and then it fixed it within Fuzzy search. Even when I remove having the extra translations appear, it is now working again. I realized the issue and then came to the forums just to browse and saw this thread, so I took a look. For me, the issue is fixed.

Andrew Batishko

Thanks for the report. I've created a case to fix this behavior.