Reproducible bug: Links to TDNT from most resources do not correctly use the prioritisation list
To reproduce this bug, prioritise TDNT over ESL (Enhanced Strong's Lexicon). Now open DBL, and click on a TDNT link. The link will open in ESL, rather than TDNT as it should. The screenshot below shows my prioritisations, and if you look at the right click menu, shows that ESL is being acted on above TDNT, despite TDNT being priotirised above ESL, and even despite TDNT being specifically selected for TDNT links.
The problem also occurs on other systems with a much simpler resource prioritisation.
I've checked the problem is several resources (DBL, Hermeneia commentaries, Eerdman's Critical Commentaries,NICOT/NICNT) and the error occurs in each one. But it does not occur in the Anchor Yale Bible Dictionary. I suspect this is because the AYBD hard links directly to the TDNT resource, rather than using the TDNT resource type as it ought to.
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!
Comments
-
What happens if you prioritize DBL (for Greek data type) above TDNT?
Dave
===Windows 11 & Android 13
0 -
Mark,
Did Logos tech ever acknowledge that this is an issue?
0 -
No - it hasn't been acknowledged, but I've filed a bug report because the List has to be predictable.
My own example:-
- VONT ==> English
- DBL Greek ==> Greek
- TDNT ==> TDNT #
- VONT (not restricted) <------------------ late EDIT
- ESL (not restricted)
Results from DBL Greek:
- TDNT # goes to ESL
- Strong's # goes to VONT
Change TDNT in List:
- VONT ==> English
- DBL Greek ==> Greek
- TDNT (not restricted)
- VONT (not restricted) <------------------ late EDIT
- ESL (not restricted)
Results from same DBL Greek links:
- TDNT # goes to TDNT
- Strong's # goes to TDNT
Predictable??
EDIT: I overlooked a VONT entry which explains how the first Strong's # result goes to VONT.
Dave
===Windows 11 & Android 13
0 -
With the volume of posts and the busy atmosphere surrounding the Logos tech team, It seems that it might be pretty easy for an important post to be overlooked.
I just wanted to check to see if the issue (or report of an issue) is acknowledged and wanted to add my two cents for addressing this issue.
Tags: unpredictable, compromise, side effects
0 -
Trey Selman said:
With the volume of posts and the busy atmosphere surrounding the Logos tech team, It seems that it might be pretty easy for an important post to be overlooked.
I just wanted to check to see if the issue (or report of an issue) is acknowledged and wanted to add my two cents for addressing this issue.
The only sure way to get a bug seen and acknowledged by Logos and be able to track its status is to log it on the wiki on the Logos 4 Bugs page.
0 -
Mark,
I'm not sure why the prioritization limits are not working as expected, but will report it.
As a workaround, add another TDNT to the priority list above the others, without advanced prioritization limits, and it will appear above the ESL on the context menu. And upon hover or left click on the link, it will display or open the TDNT to Vol 4, Page 194 (as in your example).
Melissa
0 -
Thanks Melissa.
The bug report I created in January is at http://wiki.logos.com/Bug$3a_Links_to_TDNT_from_resources_do_not_correctly_use_the_Prioritisation_List
Dave
===Windows 11 & Android 13
0 -
This has been fixed in 4.0b Beta 11.
0 -
-
Melissa Snyder said:
This has been fixed in 4.0b Beta 11.
Excellent news.
Presumably us normal (non-beta) users will get the fix when 4.0-b comes out, so I'll look forward to that.
In the meantime, just knowing it's being addressed is good news. Thanks
0 -
0
-
Mark Barnes said:
To reproduce this bug, prioritise TDNT over ESL (Enhanced Strong's Lexicon). Now open DBL, and click on a TDNT link. The link will open in ESL, rather than TDNT as it should. The screenshot below shows my prioritisations, and if you look at the right click menu, shows that ESL is being acted on above TDNT, despite TDNT being priotirised above ESL, and even despite TDNT being specifically selected for TDNT links.
The problem also occurs on other systems with a much simpler resource prioritisation.
I've checked the problem is several resources (DBL, Hermeneia commentaries, Eerdman's Critical Commentaries,NICOT/NICNT) and the error occurs in each one. But it does not occur in the Anchor Yale Bible Dictionary. I suspect this is because the AYBD hard links directly to the TDNT resource, rather than using the TDNT resource type as it ought to.
Hi all,
I'm revisiting this thread because I still have this problem. Everytime I click a TDNT link it opens in DBL (DIB according to the Spanish version of this resource) even when I have prioritized TDNT for TDNT datatype and limited DBL to DBL datatype. Here is a screenshot:
I'm running the last Windows stable version (5.2 SR-4 - 5.2.0.0110). Thanks in advance.
Blessings,
0 -
It's because you have Send hyperlinks here selected in DBL (notice the red target icon on the cover). That temporarily overrides any prioritisation.
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!
0 -
Yes, it makes sense and I couldn't figure out by myself [:$]. Thanks very much for your help Mark.
Blessings,
0
