BUG: incomplete cross-reference results

May 23, 2013

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.

Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

Comments

Sort by:

1 - 2 of 21

Mark Barnes

✭✭✭

May 25, 2013

<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.

This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

NB.Mick

May 25, 2013

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

Have joy in the Lord!

Mark Barnes

✭✭✭

May 25, 2013

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.

This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!

MJ. Smith

May 25, 2013

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

Bradley Grainger (Logos)

May 25, 2013

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.