Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another data point #1267

Open
PerpSearch opened this issue Dec 27, 2024 · 0 comments
Open

Another data point #1267

PerpSearch opened this issue Dec 27, 2024 · 0 comments

Comments

@PerpSearch
Copy link

PerpSearch commented Dec 27, 2024

Still having issues. In addition to the problem I'm having with the search function, I can't seem to access a some of my collections in the normally. This is the radial representation of my collections and the "X" is where I get the Oops error. Fortunately all the items in that whole branch are tagged so I can still pull them up with the tag so the records are still there. In an effort to fix things or get an idea what might work, I edited several records to 'move' them from one collection to another. I did about 10 records and then I was unable to access anything including the main screen. I had to restore and reinstall a few times before I could get it back up. Presently on 1.5.16, but it's no different on 1.5.13. I'm not sure how useful all this info is, but it's what I have ATM.

Thanks for your work on this project. Even with my dysfunctional application, it's still the best thing I could find for my use case.

C

(edit) More info.

A while back I set up another user account and let him add his own collection. At present it only consists of 17 items in 4 collections. The search field in the upper left corner works as it should. If I share an item that is public with the new user account, that account can view it and it can select a tag and pull up other tagged items in my collection, but if a search is attempted in that upper left search field, the 'Oops' error shows up. So at least some of my problem is in my own data set. Do we know of a way to clean it up, repair it, or re index the database or something? Clearly I don't know enough to even ask the right question, but you probably get that by now.

C

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant