BUG: Louw Nida now broken :(
Louw Nida linkages were working pretty nicely in past betas. Now it is broken (and appears to be broken similarly on the iPod?)
YES, a Bible Word Study on a greek word (after clicking a word in a Bible) brings a Louw Nida link.
YES, touching that link brings up a set of words and links from the Louw Nida index.
BUT, touching any Louw Nida numeric reference (eg 26.14 or 30.5 or 93.284 or whatever) pops up a message:
Not Available.
This used to work nicely. 
Comments
-
BUT, touching any Louw Nida numeric reference (eg 26.14 or 30.5 or 93.284 or whatever) pops up a message:
Not Available.
Definitely needs to be fixed.
Dave
===Windows 11 & Android 13
0 -
Louw Nida linkages were working pretty nicely in past betas. Now it is broken (and appears to be broken similarly on the iPod?)
YES, a Bible Word Study on a greek word (after clicking a word in a Bible) brings a Louw Nida link.
YES, touching that link brings up a set of words and links from the Louw Nida index.
BUT, touching any Louw Nida numeric reference (eg 26.14 or 30.5 or 93.284 or whatever) pops up a message:
Not Available.
This used to work nicely.
Hi Pete,
I am unable to reproduce this issue using the latest Logos test build for Android (0.9.4) on a Samsung Galaxy running Android 3.2. Can you give me more details about the tablet you are using? Thanks!
0 -
I see the same thing on an Acer Iconia A500.
0 -
I am using an Asus Transformer... and I got the same "unavailable" message the first time, but then it started to work! I do not have the resource downloaded (well, not after losing everything!!!).
0 -
I am unable to reproduce this issue using the latest Logos test build for Android (0.9.4)
To be clear, the problem occurs with any resource that displays LN numbers (e.g. LGNTI) when you tap a blue LN number. If you are using a Test build you may get different results but I'm using the latest release 0.9.4 on Samsung Galaxy S phone.
Problem also occurs in Vol 2 Greek-English Index of the Louw-Nida lexicon.
My resources are on the device and using it online or offline.
Dave
===Windows 11 & Android 13
0 -
I have resource on the phone as well (HTC Evo Shift 4G in my case.)
Perhaps that's a distinguishing factor:
- Do those who see this problem have L-N downloaded?
- Do those who do NOT see this problem NOT have L-N downloaded?
0 -
I have resource on the phone as well (HTC Evo Shift 4G in my case.)
Perhaps that's a distinguishing factor:
- Do those who see this problem have L-N downloaded?
- Do those who do NOT see this problem NOT have L-N downloaded?
I removed my LN lexicon and was able to get a definition - no definition when on the device!
Dave
===Windows 11 & Android 13
0 -
mine is not downloaded...but worked the 2nd time i tried a ln num
0 -
CONFIRMED:
- My LN was downloaded. LN links broken
- I removed the LN resource from the device. LN links work
- I re-downloaded the LN resource. LN links broken again.
So, the bug is that LN links are broken if the Louw-Nida resource is downloaded into your device.
0 -
Louw Nida linkages were working pretty nicely in past betas. Now it is broken (and appears to be broken similarly on the iPod?)
YES, a Bible Word Study on a greek word (after clicking a word in a Bible) brings a Louw Nida link.
YES, touching that link brings up a set of words and links from the Louw Nida index.
BUT, touching any Louw Nida numeric reference (eg 26.14 or 30.5 or 93.284 or whatever) pops up a message:
Not Available.
This used to work nicely.
Thanks Pete,
I will write up a case for our Development department.
0 -
Thank you for identifying the source of this bug. I thought the problem with Louw-Nida was reported a while ago, but I guess nobody determined that it occurs only when the resource is downloaded. I have removed Louw-Nida from my device, and I am happily using it again.
0 -
1.0 Beta 2 -- this bug still exists.
(If L-N is downloaded, L-N links do not work. If you do NOT download it, they still function correctly.)
0 -
1.0 Beta 2 -- this bug still exists.
(If L-N is downloaded, L-N links do not work. If you do NOT download it, they still function correctly.)
As of this time a fix has not yet been implemented.
0
