If it was just the PUI, I would guess it was an indexing problem, but that “Oops” error, to me, looks like it’s having a problem with retrieving resource tree information from the backend.
Not too long ago, there was a thread on this mailing list with the subject: "Retrieving tree info via API (what are "waypoints”?)” You might take a look at that thread and see if you can do a backend API query to fetch the resource root and it’s waypoints. Except that the “affecting all resources” sounds like something more global. What is in the log files when this happens ? — Steve M. > On Sep 16, 2019, at 3:06 PM, Zachary L Pelli <[email protected]> wrote: > > We’re running 2.5.2. On the staff interface, clicking Edit or View on any top > level resource record gives this error: “Oops! We're having trouble fetching > this tree. Please try refreshing the page.” On the PUI, you can view the > top-level record, but the “Collection Organization” tree is blank. This issue > seems to be affecting all resources. > > Regards, > > Zach Pelli > Digital Collections Infrastructure Developer > Seton Hall University Libraries > 973.275.2046 > > _______________________________________________ > Archivesspace_Users_Group mailing list > [email protected] > <mailto:[email protected]> > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
