Bug: Analysis Search
Comments
-
hummmm.... I seem to be missing them too.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
-
I should add that I see the problem on my Mac running latest Beta. Running non-Beta Logos in Windows 10 (VM) I don't have the problem.
0 -
I can reproduce this problem in the 6.8 beta and have filed a bug; thanks for reporting it.
0 -
Possibly related: https://community.logos.com/forums/t/119804.aspx
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 -
I can reproduce this problem in the 6.8 beta and have filed a bug; thanks for reporting it.
This is fixed in 6.8 RC 1.
0 -
Mark Barnes said:
Possibly related: https://community.logos.com/forums/t/119804.aspx
Today's release of 6.8 did not resolve this issue, as you can see below, I am still getting the same results: Hebrew tenses being displayed under the Greek tense heading.
0 -
Curtis M said:
Today's release of 6.8 did not resolve this issue, as you can see below, I am still getting the same results: Hebrew tenses being displayed under the Greek tense heading.
The fix related specifically to missing columns, not wrong data in the columns, which presumably means the two bugs weren't linked after all. I would imagine Faithlife will post in the other thread if/when they're able to fix that.
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 -
Mark Barnes said:
The fix related specifically to missing columns, not wrong data in the columns, which presumably means the two bugs weren't linked after all. I would imagine Faithlife will post in the other thread if/when they're able to fix that.
The case for that issue is still active, and as Mark said, we'll reply to that thread once we have a fix for it. Sorry for the inconvenience in the meantime and and confusion between these two issues. [:(]
0