L4.0bB4 and B5 "You own this resource but for some reason it's not in your library"

Tim Hensler
Tim Hensler Member Posts: 1,547 ✭✭✭

When I try to open the "Lexham Syntax Graphs of the Greek new Testament' or the "Cascadia Syntax Graphs of the new testament" a tab opens with the message "You own this resource but for some reason it's not in your library."  It has a button labeled "Update resources now" but the button is greyed out.

I looked up the problem and found someone had the same symptoms for the LEB, but the solution to that problem doesn't apply here since I did not hide any related files.  I also removed the files LexhamSGGNT.lbssyn, LexhamSGGNT.lbxclv and LexSGGlossary.logos4 from the L4 resource folder.  I launched L4.0bB5 and tried "Update Now" and also "Update Resources" both of which responded with "No updates were found."

What am I missing here?

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339

    Removal of Lexham Syntax Graphs resources will not be complete until the index is rebuilt (but wait until it is needed!)

    Have you got CSGNT.lbxclv or CSGGlossary.logos4 in \Resources?

    Did you have access to Cascadia Syntax Graphs & run Cascadia Syntax searches after the secret 4.0 beta?

    Do you have Scholar's Silver or higher?

    Dave
    ===

    Windows 11 & Android 13

  • Tim Hensler
    Tim Hensler Member Posts: 1,547 ✭✭✭

    Hi Dave,

    Removal of Lexham Syntax Graphs resources will not be complete until the index is rebuilt

    Roger that on the indexing. 


    Have you got CSGNT.lbxclv or CSGGlossary.logos4 in \Resources?

    Yes I do have both.

    Did you have access to Cascadia Syntax Graphs & run Cascadia Syntax searches after the secret 4.0 beta?

    Yes I did.

    Do you have Scholar's Silver or higher?

    I have the basic Scholar's Edition

    Thanks for your help.

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339

    I would say that you own the Cascadia from being in the secret beta but you might want to confirm the licence with Logos. If that is so, rebuilding the index would be the only way to resolve the L4 issue.

    Dave
    ===

    Windows 11 & Android 13

  • David R. McAllan
    David R. McAllan Member Posts: 296 ✭✭

    I would say that you own the Cascadia from being in the secret beta but you might want to confirm the licence with Logos. If that is so, rebuilding the index would be the only way to resolve the L4 issue.

    Actually, Dave, I followed your advise on deleting those three resources and I only have one of them still showing which is the "Cascadia Syntax Graphs of the New Testament". I have the same dilemma as Tim as he has stated above. However, I have reindexed, done the "update resources now" command and it is still showing greyed out.

    Perhaps one of the officials from Logos could enlighten us on this. I'm wondering if it is one of those books that is still being developed. It certainly says that I own the resource, but like Tim, the update is greyed out.

    David
    https://echucacommunitychurch.com

    MacBook Pro (13-inch, M1, 2020), 8 gig RAM, macOS Ventura.

  • Tim Hensler
    Tim Hensler Member Posts: 1,547 ✭✭✭

    What's interesting is that these resources used to work fine, until some time during the 4.0b beta testing (not sure exactly which beta version).

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339

    Actually, Dave, I followed your advise on deleting those three resources and I only have one of them still showing which is the "Cascadia Syntax Graphs of the New Testament". I have the same dilemma as Tim as he has stated above. However, I have reindexed, done the "update resources now" command and it is still showing greyed out.

    This whole issue has been the subject of several threads as you know and we do need an initiative from Logos to resolve it - see http://community.logos.com/forums/p/9797/78251.aspx

    Deleting seemed the only alternative now that the LexhamSGGNT resources are expired/obsolete and those that have the licence should be using Cascadia Syntax Graphs. The licence issue is not clearcut - officially you need Silver and above, but I thought it was also a "Thank you" from Logos for being in the secret beta. Now you are getting "greyed" out Cascadia resources when the message says you own it and it is in your resource file?!

    My only suggestion now is to delete CSGNT.lbxclv (21 MB) or CSGGlossary.logos4 (64 KB) and see if it is replaced!

    EDIT: I can access the 2 Cascadia resources and Cascadia Syntax search in 4.0b5, but the issue came to a head on 1 January when the beta licences expired. If the Cascadia licence was not a "Thank you" then I own it because I upgraded to Silver last year!!

    Dave
    ===

    Windows 11 & Android 13

  • Tim Hensler
    Tim Hensler Member Posts: 1,547 ✭✭✭

    Dave,

    I did the "Rebuild Index" last night but nothing changed this situation.  I'm currently teaching from the OT, so I haven't used it much during the last few weeks.  I noticed it when I started working with the 4.0b beta and was doing some research in the NT about a week ago.  I thought it (and its glossary that has the same situation) was part of the private beta thank you, but it might be they weren't and so expired on December 31 and I didn't notice.  [:'(]

    P.S. I have two entries in my library for the Lexham English Bible - one has a description in the Resource Information and the other doesn't.  The one that doesn't have a description has the same problem as my Cascadia resources.  It looks like one file/resource replaced the other but the obsolete file/resources was not removed.  I know there is another thread regarding the removal of obsolete resource files and the need for this to be automated; I guess this is another example.  How can I identify the file in the resource folder that is obsolete so I can remove it? (LEB.logos4, LEBNT.lbsrvi, LEXBIBLE.logos4, or ???)

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339

    The good resource has the interlinear bar (and doesn't give you a bad time!). So you delete LEXBIBLE.logos4.

    Dave
    ===

    Windows 11 & Android 13

This discussion has been closed.