Can someone double check me? Just reading the code and it looks like a plugin
cannot​ add multiple subrecord types. Specifically, the initializer
(https://github.com/archivesspace/archivesspace/blob/master/frontend/config/initializers/plugin.rb)
reads one config.yml file which (since its yaml)
Yeah, it's erroring on startup. I think your first suggestion that they're out
of sync with core-gems is the likely culprit.
Appreciate the quick reply and info!
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of Joshua
D. Shaw
Sent:
PS. Any errors from the AS log would help pinpoint the issue.
If it errors almost immediately on startup, I'm betting on a gem issue. If it
errors when you interact with the app, then it could be a view or method issue.
Joshua
From:
Hi Robert
It very much depends on the plugin. Things to check
1. If the plugin has a gemfile, make sure that is inline with the core gems
- ie update the plugin gem constraints if necessary
2. If the plugin overrides any core views, make sure that those overrides
incorporate any core
Hi all,
Recently upgraded a dev box from 2.5.1 to 3.3.1. First time I've worked on
updating an Archivesspace instance. Everything has gone fairly smoothly but
getting plugins sorted.
What is the process for migrating plugins successfully? I couldn't find any
documentation for
Alston,
This is a type of error I used to encounter frequently but haven't seen in the
more recent versions of ASpace. That makes me curious if you could share what
version of ArchivesSpace your are currently on? You can see this information in
the footer on any page on the staff side, like v
Hello,
We've been running into an issue periodically where archival objects won't
delete. AS returns this message: Record deletion failed:
Java::JavaSql::SQLIntegrityConstraintViolationException: Cannot delete or
update a parent row: a foreign key constraint fails
Upping the Solr timeout to 7200 seems to have prevented the commit timeout
errors. I'll be interested to see if other institutions with large repos run
into the same issue as more move to later versions of Solr. And whether the
timeout time is a moving target as the number of objects in any one
