-
Notifications
You must be signed in to change notification settings - Fork 65
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
Browse categories not updating #2968
Comments
I cannot seem to recreate this, perhaps this has been fixed in the interim. It'd be appreciated if another dev could try and confirm/deny. |
@taylor-steve I tried this out and browse categories also worked for me correctly when I had made the categories public. On widget in page, shows 6 items (after starting with 4 and then adding 2) |
I also cannot duplicate this problem. If I add a tag to an item they show up right away in the browse category built from that tag. |
Is it possibly related to bulk tagging? Reindex busts the exhibits cache with: https://github.com/projectblacklight/spotlight/blob/main/app/jobs/spotlight/reindex_job.rb#L20 But I don't see anything similar in (I mean, it's also possible acts-as-taggable does it under the hood now 🤷) |
Bulk tagging is a good thought. I tried a few variations during my attempt to recreate without any luck. I'm inclined to close this for now and re-open if it reoccurs. Any objections, or do folks feel this is serious enough to dig through previous versions to replicate/isolate the issue? |
I’m getting some unexpected behavior using exhibit tags to make browse categories and want to check to see if this is a bug or if its how browse categories are supposed to work.
I was expecting the browse category to include these new records but it doesn’t. I then manually selected the linked tag from one of the records which led back to a search result of all records with that tag. I tried to "update the existing category" from those results but the category was not updated.
This seems to resolve after clearing the rails cache, so there seems to be some place where we aren't poisoning the cache.
Moved from sul-dlss/dlme#1753
The text was updated successfully, but these errors were encountered: