Open jeremyf opened 1 year ago
In testing it appears that there is something out of sorts with this particular collection.
I have checked for reported exceptions in Sentry (our exception tracker) and am not seeing anything reported.
I checked the system logs and for the request (see https://playbook-staging.notch8.com/en/dev/rails-logging-and-understanding-the-elements-of-a-line-in-the-logs for some of the details)
Note: I am not able to duplicate this error locally.
I moved this back to "No Status" as there is a known work around; this also lets us prioritize other work per @KatharineV's direction.
There may be a relation to scientist-softserv/adventist-dl#131
Just dropping in to add that all collections fail to update visibility settings if and only if there is a file uploaded as the logo.
Note There is a work around. The problem is related to the save process not finding an image. To work around, remove the image, save, change the visibility, save, then re-add the image, and save.
There is a details Slack thread that outlines some of the nuances of the below listed collection. tl;dr - It appears to be the uploaded Logo that is a problem.
Acceptance Criteria
The specific collection that requires updating is https://adl.b2.adventistdigitallibrary.org/collections/11aab197-b630-48c0-91cd-1578d42d9f53?locale=en
Notes
This behavior also exists in https://adl.b2.adventistdigitallibrary.org/collections/8216c9e8-fbe7-4271-a88c-da890a9eeb8c?locale=en