Bug: Biblical Places/People/Things showing unprioritized resources first

Todd Phillips

The Biblical Places, People and Things windows are showing unprioritized resources at the start of the dictionary listing. Not sure when this started happening.

In this Biblical Places example, IMCB (Illustrated Manners and Customs of the Bible) and WHGBL (Wycliffe Historical Geography of Bible Lands) show at the start of the list even though they are NOT prioritized.  The rest of the displayed dictionaries are in prioritized order (starting with ISBE):

Putting IMCB and WHGBL into my preferred resources list does nothing to change the displayed order.  Something is wrong. 

They also show up in the right-click menu under the Place tab:

A similar problem can be seen in the Biblical People window. IMCB and EMB (Every Man in the Bible) are unwanted and unprioritized, but still show up:

For me, ISBE is the highest prioritized dictionary, and it should be the first entry in all of these lists, rather than IMCB, WHGBL or EMB.  The problem happens in Biblical People, too, though I didn't post an example.

This is similar to a bug I reported a year ago regarding these resources appearing the Topic section of the search window: http://community.logos.com/forums/p/31182/231252.aspx.  That bug was fixed so that the unprioritized resources no longer show up at the start in the Topic search, but it seems to be the same (or similar) problem.

Dave Hooton

Todd Phillips said:

This is similar to a bug I reported a year ago regarding these resources appearing the Topic section of the search window: http://community.logos.com/forums/p/31182/231252.aspx.  That bug was fixed so that the unprioritized resources no longer show up at the start in the Topic search, but it seems to be the same (or similar) problem.

The Places problem also occurs in 4.5a, but not in the Topic Section of Basic Search (where IMCB is last). IMCB is not prioritised; otherwise my prioritised resources appear correctly.

Bradley Grainger (Logos)

I have reproduced this bug and fixed it.

The fix probably won't make it into the next beta release, but will be in the one after that.