Bug: L4 loads resource from L3 rather than downloading

I hid a resource, restarted L4 & noted that my resource count was one less and the resource was not in Library. Then unhid the resource and restarted L4. Indexing started but i noted it was lbxlls from L3 resource folder and a supplementary index had been created. A download notification told me that the Logos4 file was available. No indexing took place and and the supplementary index remained. I performed a "Merge index" to get rid of it.

Issue: L4 shouldn't be grabbing "missing" files from my L3 folder

EDIT: highlighting of search results for words like "prayer" "holy" is misaligned because of the incorrect indexing

Find more posts tagged with

Comments

Dave Hooton

EDIT: highlighting of search results for words like "prayer" "holy" is misaligned because of the incorrect indexing

I was able to correct the misalignment by repeating the hide/unhide + Merge process, taking care that the L3 resource would not be used. On the positive side Merge did not duplicate index entries for the resource & removed the incorrect entries from the Main index.

Melissa Snyder

I've reported this.

JimTowler

https://community.logos.com/discussion/comment/140463#Comment_140463

Can the "Scan L3" be made an option just like we have now with "Scan <dirname>" and "Scan DVD", rather than automatic?

(It would have made this bug report never have happened)

Dave Hooton

https://community.logos.com/discussion/comment/140697#Comment_140697

Can the "Scan L3" be made an option just like we have now with "Scan <dirname>" and "Scan DVD", rather than automatic

It took a re-read but I know what you mean! L4 shouldn't be grabbing "missing" files from my L3 folder in this unhide situation. In general, I don't think the Indexer should be looking at L3 resources as this has caused too many problems and I think it should now be optional for the L4 Installer. If we notice any "missing" resources after a download then "scan L3" would be a good way to specify the L3 resource folder!

NetworkGeek

https://community.logos.com/discussion/comment/140728#Comment_140728

Dave, isn't this the same problem as the Galaxie files problem where copies of files come from L3 instead of from the L4 servers? We have suffered from that one forever, it's why I have to keep my Logos 3 resources folder renamed most of the time so L4 won't grab files from there when the lbxlls was updated later than a logos4 file...

Dave Hooton

https://community.logos.com/discussion/comment/140737#Comment_140737

Dave, isn't this the same problem as the Galaxie files problem where copies of files come from L3 instead of from the L4 servers? We have suffered from that one forever, it's why I have to keep my Logos 3 resources folder renamed most of the time so L4 won't grab files from there when the lbxlls was updated later than a logos4 file...

It is similar but there is no download loop and I don't have to shield my L3 resources from L4. If Logos will agree that the Indexer should never take resources from L3 then it will benefit both situations. It was helpful in the beginning but now it causes too many problems.

Melissa Snyder

https://community.logos.com/discussion/comment/140746#Comment_140746

It is similar but there is no download loop and I don't have to shield my L3 resources from L4. If Logos will agree that the Indexer should never take resources from L3 then it will benefit both situations. It was helpful in the beginning but now it causes too many problems.

Development does not see a problem with this and says it is by design. The system is designed to try to find books locally when possible. (There are 9,000 books that haven't been converted to Logos 4 format yet.)

Dave Hooton

https://community.logos.com/discussion/comment/141253#Comment_141253

Development does not see a problem with this and says it is by design. The system is designed to try to find books locally when possible. (There are 9,000 books that haven't been converted to Logos 4 format yet.)

I'm sorry Melissa but that does not answer the problem! If L4 did not have a resource path for L3 where would it get the resource from? It would have got it from the L4 server AND it would have been logos4 format AND I would not have had this issue. IF instead, the resource (from L4 server) was in L3 format at least there would have been no conflict such as I reported for Jeremiah Lifeworks Quick Start Guide (except for being the wrong version!).

I assumed that the L4 server had the 9000 L3 books because they aren't on my computer! All I'm asking is that L4 not automatically assume I have L3 resources that take precedence over resources on the L4 server.

JimTowler

https://community.logos.com/discussion/comment/141253#Comment_141253

Development does not see a problem with this and says it is by design.

Please tell Development that there are L4 users that RENAME their L3 directories so L4 does NOT do this thing, which can't be disabled!!!

Tell them too, of the reports here where people are having issues because of this rigid and unwanted design.

Please add an option so it can be disabled for those that don't want it. That something is "By Design" is no useful answer when it leads to pain and can't be disabled.

MJ. Smith

https://community.logos.com/discussion/comment/141283#Comment_141283

All I'm asking is that L4 not automatically assume I have L3 resources that take precedence over resources on the L4 server.

It seems to me that even if L4 grabs the L3 files that it should be verifying that they are the latest files. The idea of grabbing file from the hard drive to save network traffic is solid - but works in practice only if one also checks that the L3 file is current. As L3 gets used less of the time it becomes more likely that it is an old copy of the resource. Verifying the date/version is critical.

JimTowler

https://community.logos.com/discussion/comment/141377#Comment_141377

The idea of grabbing file from the hard drive to save network traffic is solid - but works in practice only if one also checks that the L3 file is current.

YES - its a great design to use a file thats already here, if its FIRST confirmed that its the most current!

NetworkGeek

https://community.logos.com/discussion/comment/141382#Comment_141382

YES - its a great design to use a file thats already here, if its FIRST confirmed that its the most current!

And therein lies the problem. For me with Galaxie files, whether it's some anomaly in the capitalization of the filename, or file version (vs. the true resource version), Logos 4 will copy form Logos 3, then copy from Logos 4 servers, then start all over again in an endless cycle. Bradley saw this, which is why he took the Galaxie updates off the server for awhile. It seems this should not be that difficult to solve logically, but it's been 6 months and I do grow weary of always hiding my Logos 3 Resources folder when I want to work in Logos 4 on my laptop.

JimTowler

https://community.logos.com/discussion/comment/141469#Comment_141469

The solution is really simple.

Don't automatically take L3 content into L4!!!

Add an option to the program settings, so it can be disabled for those users that are impacted. Or make it hidden, so those impacted can run "Set L3 autoscan to no" or something. Solved!!!

Please Logos, add some of these simple user-options for those that need them.