BUG: Library not Displaying All MetaData
Comments
-
Other people have seen similar problems - see https://community.logos.com/forums/t/96509.aspx for an example discussion.
What version of Logos 6 are you running and on which platform?
0 -
Mine just started doing this today. Never had a problem before.
Logos Bible Software 6.0a SR-2
6.0.1.1328Windows 7 64 bit.
0 -
I'm using 6.0a SR-3 6.0.1.1339 as of today , but I think there was an update since I initiated this thread. I have updates set to download immediately. I'll keep monitoring it.
0 -
It began working again with SR-2 the day after I posted that (must be an intermittent problem), but hasn't worked since I've upgraded to SR-3.
0 -
Closing and re-opening Library usually works.
It would be good to hear from Faithlife.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Closing and re-opening Library usually works.
It would be good to hear from Faithlife.
Yes, it would be good to hear an official response from Faithlife/Logos. The issue still exists in Beta 3.
0 -
Erwin Stull, Sr. said:
Yes, it would be good to hear an official response from Faithlife/Logos. The issue still exists in Beta 3.
Previously I hadn't been able to reproduce this, but I was able to this morning. I didn't see anything relevant in my logs, but I'll create a case for development to look into it and see if they can figure out what's happening.
0 -
Dylan Rondeau said:Erwin Stull, Sr. said:
Yes, it would be good to hear an official response from Faithlife/Logos. The issue still exists in Beta 3.
Previously I hadn't been able to reproduce this, but I was able to this morning. I didn't see anything relevant in my logs, but I'll create a case for development to look into it and see if they can figure out what's happening.
Thanks, Dylan
0 -
Thanks, Dylan!
0 -
Erwin Stull, Sr. said:Dylan Rondeau said:Erwin Stull, Sr. said:
Yes, it would be good to hear an official response from Faithlife/Logos. The issue still exists in Beta 3.
Previously I hadn't been able to reproduce this, but I was able to this morning. I didn't see anything relevant in my logs, but I'll create a case for development to look into it and see if they can figure out what's happening.
Thanks, Dylan
This has been fixed in 6.0b, which is now available for stable users.
0