BUG: incomplete cross-reference results

See http://community.logos.com/forums/p/70608/491642.aspx#491642 for how this was found. Note the incomplete results in the Cross-reference section.

Find more posts tagged with

Comments

Mark Barnes

<edit>We worked out the exact nature of the bug. If you want to jump to that post, it's here.</edit>

To clarify, most users are seeing this:

But it should look like this:

So there are two aspects to the bug report:

Why is MJ seeing only Wisdom 10:3.
Why most other users, despite owning NABRE, are not seeing Wisdom 10:3 at all.

NB.Mick

So there are two aspects to the bug report:

Why is MJ seeing only Wisdom 10:3.

Why most other users, despite owning NABRE, are not seeing Wisdom 10:3 at all.

Re: 2 this seems to be relative to the currently preferred bible, see http://community.logos.com/forums/p/70608/492143.aspx#492143

Mark Barnes

To summarise for the Logos engineers

The problem is definitely related to the most highly prioritised Bible that isn't using advanced prioritisation to limit it to only one resource.
It seems that the problem relates to the datatype of that preferred Bible. Apparently, only passages that are "valid" according to that datatype are displayed. This causes these problems:

If your most highly prioritised Bible uses a Septuagint datatype, you'll never see any NT references.
If your most highly prioritised Bible uses a protestant canon datatype, you'll never see any apocryphal references.
If your most highly prioritised Bible uses an NT datatype, you'll never see OT or apocrypha references.

MJ. Smith

excellent sleuthing. EDIT: I just checked my priorities which modifies the first statement in the summary:

Bradley Grainger (Logos)

To summarise for the Logos engineers

The problem is definitely related to the most highly prioritised Bible

Thank you very much for the detailed detective work. I tried (quickly) to repro this on Thursday, but couldn't and shelved the bug for later, more detailed analysis.

Now that you've identified the problem, I've fixed it. The fix will probably won't be in Beta 9 (since we're past the cutoff for changes for that), but should be available in the subsequent release.

Brisa Davis

This will be fixed in 5.1 Beta 9.

Bradley Grainger (Logos)

We found a similar issue in the "Cross References" section in the Explorer tool. This will be fixed after Beta 9.

Brisa Davis

We found a similar issue in the "Cross References" section in the Explorer tool.

This will be fixed in 5.1 RC 1.