Case 1: Psalm 11 becomes Psalm 2
All panes closed before next test:
Case 2: Psalm 23 becomes Psalm 15
Case 3 works correctly
Here here... I have avoided reporting it but it is annoying having to go through a dozen links to find the right one...
-Dan
PS: Is this issue Logos wide or just those of us using verbum?
Thanks for pointing this out. The code that navigates within a resource is probably assuming that a "Bible Commentary" covers most of the biblical book it is commenting on, and also covers it in biblical book order. I suspect it wasn't designed to handle a resource that has sparse coverage (e.g., Psalm 2, 15, 27, 29, ...) particularly when those sections of the resource are "out of order".
We can look into this; for now, I would suggest having this series as your second-highest, not most-prioritised, commentary.
Bradley, this worked correctly as I started from the Lectionary on the home page ... and continued as I clicked on each reading ... but when I clicked on the first reading it decided to randomize again. I'd given first priority to:
LLS:LECTCOMM12013-02-05T17:26:18ZLECTCOMM1.logos4
I suspect all lectionary based Bible commentaries have a similar problem. Of course, their link to the Lectionary is logically liturgical date but ...
Thanks so much for reporting this! I've noticed weird stuff when working through the lectionary but wasn't sure how far the issue went. Upping the priority is a good way to isolate it.
I deleted my previous posts, because I sent us on a rabbit trail by getting my facts wrong. Let's start over again:
What were you expecting to happen here? Feasting on the Word doesn't have any commentary on Psalm 11 [12], so it opens to the "nearest" (which, in this case, is strangely defined because the milestones for Psalms are spread across 12 resources).
Interesting. It opens Year A, Volume 1 but as soon as you scroll in a Bible pane, it correctly changes to Year B, Volume 4.
so it opens to the "nearest" (which, in this case, is strangely defined because the milestones for Psalms are spread across 12 resources).
I would accept this answer as long as I can understand what "nearest" is in this situation.
I'm glad you saw this as I had similar unexpected behavior here and there but could never capture and define it. What I suspect unfortunately is that the lectionary based commentaries should not be classified as type:Bible Commentary but ultimately need a type:Lectionary Commentary ... which means unless you have a surprise for me they may all need to be type:Monograph or type:Commentary for now.