Duplicating Search Results
On my work Mac, I am getting duplicating Bible search results. This happens no matter what Bible I search and even after a reindex.
Any ideas what is happening and how to fix it?
This appears to be unique to this one particular installation. It doesn't happen on my personal Mac.
Comments
-
Click the icon at top right, above the Search box.
The little down-arrow enables you to choose the Additional Version in Search.Dave
===Windows 11 & Android 13
0 -
Thanks for the reply, Dave, but there are still weird duplicate issues. That did take care of the problem in that search, but I'm still getting duplicate results in other searches.
Notice at the end of the canonical listing, the results begin to repeat here and the multiple resources display isn't checked here:
0 -
-
... I'm still getting duplicate results in other searches.
I can't reproduce those duplicates Try the command reindex lhb in Command Box (in the App toolbar); which will re-index the LHB. Do you get this with other bibles?
Dave
===Windows 11 & Android 13
0 -
Yeah, I can’t reproduce it on my other machine either. I have reindexed my whole library and individual bibles. Yes, it happens with multiple Bibles.
0 -
Yeah, I can’t reproduce it on my other machine either. I have reindexed my whole library and individual bibles. Yes, it happens with multiple Bibles.
Does it happen if you close the Search tab and use a new one?
Dave
===Windows 11 & Android 13
0 -
Hi Brian--Sorry for the trouble here. Sounds like your library index has gotten into some weird state. The solution will probably be to totally blow it away and let the application rebuild it. But if you don't mind, would you check a few things for us first? It might help us to understand how you've gotten into this state so we can prevent others from getting into the same position.
First, close the application completely.
If you've previously enabled logging, you might have some logs that would be helpful for us. Or if you haven't, and you're up for it, might be good to enable logging. The instructions for enabling logging and/or fetching logs can be found here. This might help us to understand what's going on, but if you don't have time right now and just want to get your problem fixed, feel free to skip this step.
Now you'll want to go find your library index files. They're located in a folder that mac keeps hidden, so you'll want to open finder, go to /Users/{your username} and press cmd + shift + . (all at the same time) to show hidden files and folders. Once you do that, you should see the `Library` folder. From there you'll be able to get to your index files. The full path to your library index files is `/Users/{your username}/Library/Application Support/Logos4/Data/{some random folder name}/Library Index`.
Once you're there (in the `Library Index` folder) it would be helpful for us to have a list of all the files in that folder. Could you share that with us? Also, it would be great if you could upload here the `LibraryIndex.db` file. It might help us to better understand what's happened.
After you've (hopefully) made note of the filenames in that folder and grabbed the `LibraryIndex.db` file to share with us, go ahead and delete that entire `Library Index` folder.
After you've deleted it, start up the application, and it should automatically start rebuilding the index. This is similar to doing a `rebuild index` in the command box, so it'll take some time, but is usually an effective way to resolve any corruption in the index, even if the problem isn't resolved by the `rebuild index` command.
Hope this does the trick. Keep us posted. And thanks for posting the issue here.
-Ronny
0 -
Ronny,
Sorry I missed this message. I'm attaching the file names and the .db file itself.
0 -
I deleted the folder and allowed the program to build the index again.
The problem persists.
0 -
Man, sorry to hear that Brian. I'll admit I'm a bit perplexed here, but will do a little 'circling of the wagons' with the team to see if we can't get some other ideas of what might be happening and how we might fix it for you.
One other thing on my end I can think of...it's a bit of a shot in the dark...let's have a look at your personal book index. Maybe some of your bibles ended up getting duplicated in there somehow. In the same location as your LibraryIndex folder, you should (I think) have a 'PersonalBookIndex' folder. Could you do the same thing with that folder that you did with the `LibraryIndex` one (i.e. screenshot me the contents of that folder, share the `LibraryIndex.db` file, and then blow away the whole folder, and start up the application so that it will rebuild that index...which btw should be much faster and less disruptive than rebuilding your entire normal index)?
Keep us posted and we'll do the same as we have other ideas/questions/etc.
Thanks,
-Ronny
0 -
Ha, oops, I was logged in with one of my testing accounts when I posted above and didn't realize. Anyway, ignore the confusing user profile on the above post. It was me
0 -
Thanks for your time.
Here is the LibraryIndex.db file from the PersonalBookIndex folder:
On additional note: In Bible Word Study I don't get duplicate results. It's only in the search tab.
0 -
-
Interesting. Yeah, from the .db file you attached, it looks like 122 books somehow ended up in your Personal Book Index. Not sure how that would have happened (let us know if you have any inkling), but I'm really glad we got it fixed. Hopefully won't ever happen again but let us know if you have anymore trouble. Thanks!
-Ronny
0 -
-
I was having the same issue. So if it is helpful in finding how this is occurring here are my files.
0 -
Thanks for sharing Eric. How long was it occurring for you? Can you think of anything notable that happened around the time you started noticing the issue? e.g. did you reindex your library, or even any particular resources?
0 -
I don't recall when it started happening but I've ignored it for awhile. I don't recall anything in particular happening in conjunction with it. I also do not reindex my library on my own.
Wish I could be more helpful. For some reason I decided to search the forums today to see if there was a way to fix it and ran across this thread.
0
