ERROR? UNIQUE BUG? W7 -- Beta 9 - I've Never before seen the "wrong" resources appear in a PG C
[I am only posting here, rather than in General, because I am running beta].
I ran this PG twice. Each time it gave the exact same incorrect result. I edited it by re-naming the Collection BUT still received these same incorrect results.
My collection on the left side of "snip" is named: Collections_Commentaries_09 Hymn
(Seen on the right) is a "snipping" from my Passage Guide using that Collection: The "wrong" Resources appear. It appears to be a very "eclectic" choice BUT NONE have to do with "hymns."
(As mentioned above) I even tried to re-name the Collection, but it resulted in the same [in-correct] results.
This Collection option in my PG guide has worked fine, up to now--also this is an entirely "chosen" collection, ie it is not dynamic. That has never mattered until now.
Any suggestions as to why? Although this is in "error" it is NOT a "crash" scenario.
[I've never seen this - I've run L5 since it's beginning as did Logos 4 since inception etc]
My Logs-from oldest to newest::
From previous Stable Release Version:
From later Stable Release Version:
Crash log from earlier Beta version:
Latest up-to-date L5 Log:
I assume that this last log would be the only one to show "anything", if such information even appears in a log?
QUESTION: Is it "substituting" because there are NO "hymns" to display? If there are no results then usually I would just get "no results"
QUESTION: Why, even after re-naming the Collection, do the same in-correct results appear?:
Curious--and wishing for some "true" hymn results [:)]
I do not ever remember seeing this issue reported on these Forums?
Thanks
Regards, SteveF
Comments
-
-
I can reproduce this and have filed a bug.
0 -
Regards, SteveF
0 -
Bradley Grainger (Logos) said:
I can reproduce this and have filed a bug.
This will be fixed in the final release of 5.1; thanks for reporting it.
0 -
Bradley Grainger (Logos) said:
This will be fixed in the final release of 5.1; thanks for reporting it.
Thanks again, Bradley, as I was really afraid that it must have been something that I had done to "break it" -- Relieved!
Regards, SteveF
0