[Archivesspace_Users_Group] Error when saving records in 2.2.2

Custer, Mark mark.custer at yale.edu
Tue Jan 2 13:35:47 EST 2018

Hi, Trevor:

I don’t think that we’ve seen this particular issue, but we did have another issue when upgrading from 1.5.x to 2.x which I’ll mention here in case it’s of any use in your circumstance.  For us, the issue was simply a plugin.  In our case, whenever we saved a record after upgrading, the user was forced to re-load the page in order for the entire page to refresh correctly so that the user could get on with their work.  The problem was that the plugin overrode some new code in the 2.x version of the application, specifically the Enable Reorder Mode button that’s now part of the Edit mode, which resulted in a javascript error whenever a new archival object was added.  Once we updated the plugin to be 2.x compliant, though, everything behaved as expected again with the plugin turned on.

Do you have any plugins in your instance that could be causing this issue?  Just based on that experience, I’d want to rule out that possibility first.


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Trevor Thornton
Sent: Tuesday, 02 January, 2018 11:49 AM
To: Archivesspace <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Error when saving records in 2.2.2

Hi everybody-

Since we updated to 2.2.2 we have had an inconsistently recurring issue when creating and editing records. When the user saves the record they are immediately given an error message indicating that the record did not save (sometimes the message is "Failed to save your changes", sometimes it's "Record not found"). But upon refreshing the page it turns out that the changes actually did save, and there are no errors logged on the backend, which makes me think it's just a frontend issue. This has happened so far with resource, archival object, subject and agent records.

It doesn't happen every time, which is kind of good, but it makes it impossible to reliably reproduce the problem - the same set of actions that triggered the error once will not necessarily trigger it a second time. This makes it hard to diagnose what's going on or to report the issue in a helpful way.

Has anyone else noticed anything like this?


Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180102/13880d91/attachment.html>

More information about the Archivesspace_Users_Group mailing list