Logos 6.10 (6.10.0.0026) available for download

Update:

We have removed the update to 6.10 for more information see this post.

Logos 6.10 (6.10.0.0026) is available for download.

If you have automatic updates turned on, 6.10 will be downloaded automatically the next time your system checks for updates. To install it right away, enter the Update Now command. If you encounter problems with the auto update, download 6.10 using the appropriate link:

Links removed

Release Notes

This release includes:

Logos Now: Miracles of the Bible - A New interactive, Miracles of the Bible, classifies miracles that occur in the Old and New Testaments according to various criteria.
Logos Now: Resource Panel - When a lexicon and a Bible are in the same linkset, and you have left clicked on a word in the surface text of the Bible, the lexicon will navigate to the definition for the associated lemma.
Logos Now: Supplemental Data - Added Syntactic Force and Miracles Dataset.
All users: Morph Search - Morph searches are no longer constrained by a single morphology. Previously, the resources that would be searched in were **only** those that supported the selected morphology. The workflow has now changed. Rather than selecting a morphology, first select the resources and references to search in. These constrain the available morphologies to select from, which are now presented in the morph picker control (the popup that appears after typing “@”.)
All users: Passage Guide - Added the ability to select a particular number of commentaries to load, this can be set in your template or by clicking settings and entering the number of commentaries you want to see in this section, then right-clicking on the commentaries header and selecting the refresh button.
All users: Factbook- Added Journals section to the Factbook.
All users: Bible Search - Added Pericopes to the reference selector.
Numerous bug and crash fixes

Find more posts tagged with

Comments

John Kight

I looks like the Mac download link is for Logos 5. Do you have the Logos 6.10 file link?

Bill Shewmaker

https://community.logos.com/discussion/comment/808510#Comment_808510

When I tried this link, it was for Logos 5 as well (on a PC). Consequently when I tried to download, it said that there was newer version already installed. L6.9 SR-1.

Steve Workman

https://community.logos.com/discussion/comment/808516#Comment_808516

When I tried this link, it was for Logos 5 as well (on a PC). Consequently when I tried to download, it said that there was newer version already installed. L6.9 SR-1.

Sorry about that, I have updated the links and they should work properly now.

Bill Shewmaker

https://community.logos.com/discussion/comment/808520#Comment_808520

Thank you for the new link...now running 6.10

Brian Losabia

Cool, it looks like the Catholic Lectionary supports Red Letter settings for the Words of Christ (in translations which support the feature). Thanks Faithlife.

Veli Voipio

https://community.logos.com/discussion/comment/808569#Comment_808569

Also for Logos now, the Reader's edition for Hebrew interlinear seems to work fine. [H]

Don Awalt

https://community.logos.com/discussion/comment/808569#Comment_808569

Cool, it looks like the Catholic Lectionary supports Red Letter settings for the Words of Christ (in translations which support the feature). Thanks Faithlife.

Brian, where are you seeing this - in Basic searching the Catholic Lectionary as an option? I have tried red-letter Bibles inside the Lectionary and don't see it...

Martin Folley

My auto update is on ... but no update ... and update now does not do the trick either.

What did happen automatically yesterday evening was an update to 6.9 SR-1 (6.9.0.0044).

Brian Losabia

https://community.logos.com/discussion/comment/808633#Comment_808633

Hi Don,

Hmm, I wonder now if it might be some Logos Now/Verbum Now feature, since I do have a Verbum Now subscription. I have the following overall program setting configured: Tools > Program Settings > Show Red Letter in Bibles: YES . Since the update to 6.10, if I drop down the tranlation box at the top of the Catholic Lectionary and pick a red letter Bible (e.g. NLT, NIV, NRSV, KJV, etc.), the Words of Christ (in the Gospel lection) will show up in red. Is that how your program settings are configured?

Don Awalt

https://community.logos.com/discussion/comment/808645#Comment_808645

Hi Don,

Hmm, I wonder now if it might be some Logos Now/Verbum Now feature, since I do have a Verbum Now subscription. I have the following overall program setting configured: Tools > Program Settings > Show Red Letter in Bibles: YES . Since the update to 6.10, if I drop down the tranlation box at the top of the Catholic Lectionary and pick a red letter Bible (e.g. NLT, NIV, NRSV, KJV, etc.), the Words of Christ (in the Gospel lection) will show up in red. Is that how your program settings are configured?

Ah that works - I was not sure where you were seeing the red letter verses, I was confused with searches. Thanks Brian, all cleared up!

danwdoo

So far this version seems to be a lot more snappy, especially related to the interface. Used to be that if I left Logos minimized, there was a bit of delay when switching back before any interface buttons would work and the disk would thrash away. So far, everything seems much quicker with none of the disk activity from switching to the program. Perhaps the updates to the back end helped on this one. Either way I'm happy!

Stephen Steele

All users: Passage Guide - Added the ability to select a particular number of commentaries to load, this can be set in your template or by clicking settings and entering the number of commentaries you want to see in this section, then right-clicking on the commentaries header and selecting the refresh button.

[y]

Andrew Zoll

https://community.logos.com/discussion/comment/808909#Comment_808909

With this version, Logos crashes every time I try to open the NLT with visual filters enabled. :-(

Graham Criddle

https://community.logos.com/discussion/comment/808919#Comment_808919

With this version, Logos crashes every time I try to open the NLT with visual filters enabled. :-(

Doesn't happen for me on Windows.

I suggest you start a new thread providing as much information as possible and posting logs

Sarel Slabbert

https://community.logos.com/discussion/comment/808634#Comment_808634

My auto update is on ... but no update ... and update now does not do the trick either.

What did happen automatically yesterday evening was an update to 6.9 SR-1 (6.9.0.0044).

Same for me. Currently running 6.9 SR-1 (6.9.0.0044) after an update yesterday. Update Now indicates: "No Updates were found."

Strange

Gareth Harker

This update installed yesterday concurrent with some Windows updates. Now Logos crashes whenever I try to navigate to the last passage I was working on in any Bible translation. I can navigate to pretty much any other passage in the Bible, just not the one I was working on when the update was installed. Does anyone else have a similar problem?

Graham Criddle

https://community.logos.com/discussion/comment/808965#Comment_808965

Hi Gareth - and welcome to the forums

Sorry to hear you are having problems.

Does anyone else have a similar problem?

I haven't seen anything similar reported

Please start a new thread providing as many details as possible and posting diagnostic logs after a crash as per https://www.logos.com/support/logos6/windows/report-problem

Graham

Sean

Did this update get pulled or something?

The other day when it came out it showed I had an update waiting to download of something like 250MB. (I am a Logos Now subscriber.) Busy at the time, I was only able to use Logos again today, and the size of the update had dropped down to 95MB. After downloading, I am still on 6.9.0.0044. "Update Now" does not show anything else pending.

Sarel Slabbert

https://community.logos.com/discussion/comment/809071#Comment_809071

Did this update get pulled or something?

The other day when it came out it showed I had an update waiting to download of something like 250MB. (I am a Logos Now subscriber.) Busy at the time, I was only able to use Logos again today, and the size of the update had dropped down to 95MB. After downloading, I am still on 6.9.0.0044. "Update Now" does not show anything else pending.

Same here. I had a big update, and then, after I started upgrading the size dropped. Still running 6.9.0.0044. Update Now still shows "No Updates were found" Strange

Jack Caviness

https://community.logos.com/discussion/comment/809085#Comment_809085

Did this update get pulled or something?

The other day when it came out it showed I had an update waiting to download of something like 250MB. (I am a Logos Now subscriber.) Busy at the time, I was only able to use Logos again today, and the size of the update had dropped down to 95MB. After downloading, I am still on 6.9.0.0044. "Update Now" does not show anything else pending.

Same here. I had a big update, and then, after I started upgrading the size dropped. Still running 6.9.0.0044. Update Now still shows "No Updates were found" Strange

Try a manual install—See the link in my signature line.

Schumitinu

https://community.logos.com/discussion/comment/808919#Comment_808919

With this version, Logos crashes every time I try to open the NLT with visual filters enabled. :-(

Sounds to me like your index is broken. You might want to use Logos Logging Utility to create a log and see whether your index is still working or not. This happened to me when I updated to L6.10 on my MacBook Pro.

Graham Criddle

https://community.logos.com/discussion/comment/809114#Comment_809114

With this version, Logos crashes every time I try to open the NLT with visual filters enabled. :-(

Sounds to me like your index is broken. You might want to use Logos Logging Utility to create a log and see whether your index is still working or not. This happened to me when I updated to L6.10 on my MacBook Pro.

Faithlife has recognised this as an issue and are working on it as per https://community.logos.com/forums/p/123858/809013.aspx#809013

Ryan Gano (Logos)

https://community.logos.com/discussion/comment/809085#Comment_809085

There were a few unexpected issues with this build that we've been working behind the scenes to correct:

Crash opening resources
Crash opening Factbook (I'm not sure we have a forum post about this)
Constant reindexing on Mac

We have fixes for the first two but the third has been more difficult to track down. We will be pulling 6.10 back so it doesn't automatically download for users that haven't yet upgraded.

We do plan to release a build later today to fix the first two issues. It will need to be manually downloaded until we correct the indexing issue so we will post a link in this thread to get the updated build.

David Wanat

https://community.logos.com/discussion/comment/809156#Comment_809156

Interesting. I have not had these problems, but I do not use Logos/Verbum Now.

Sarel Slabbert

https://community.logos.com/discussion/comment/809106#Comment_809106

Did this update get pulled or something?

The other day when it came out it showed I had an update waiting to download of something like 250MB. (I am a Logos Now subscriber.) Busy at the time, I was only able to use Logos again today, and the size of the update had dropped down to 95MB. After downloading, I am still on 6.9.0.0044. "Update Now" does not show anything else pending.

Same here. I had a big update, and then, after I started upgrading the size dropped. Still running 6.9.0.0044. Update Now still shows "No Updates were found" Strange

Try a manual install—See the link in my signature line.

Thanks, that did the trick

Sean

https://community.logos.com/discussion/comment/809373#Comment_809373

Umm, they have pulled the update because bugs some users were experiencing. I don't think it's a good idea to install it right now even if that link still works.

Andrew Batishko

https://community.logos.com/discussion/comment/809382#Comment_809382

Umm, they have pulled the update because bugs some users were experiencing. I don't think it's a good idea to install it right now even if that link still works.

The install link currently points to the 6.9 release, not the 6.10 release.