All dates in the "Dates" section of a record are indexed for use in
date-range searches, regardless of the label.
For example, if something was created between 1880 and 1885, but it was
also published in June 1950, and digitized on 4th May 2010, then it'll
be indexed with the years 1880, 1881,
Hello all,
In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
encountering the following error on startup:
Dec 05, 2022 8:23:43 PM
org.eclipse.jetty.server.handler.ContextHandler$Context log
WARNING: ERROR: initialization failed
org.jruby.rack.RackInitializationExceptio
Be sure to run the initialize_plugin script again after the upgrade.
Tom
On Tue, Dec 6, 2022 at 2:06 PM David P. Steelman wrote:
> Hello all,
>
> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
> encountering the following error on startup:
>
>
> Dec 05, 2022 8:23:43 P
Try using the latest tag version on that plugin.
https://github.com/lyrasis/aspace-oauth/tags
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
on behalf of David P.
Steelman
Sent: Tuesday, December 6, 2022 2:02 PM
To: Archivesspace Users Group
S
There was a version of the aspace-oauth plugin in which the public_suffix
gem did not compile. I remember having some problems with that.
I just rebuilt mine here and it looks like the current version is working
right, with the 4.0.7 version. So it may help to simply download again.
Tom
On Tue,
Thanks for the quick responses.
I have tried using aspace-oauth v3.2.0, and am running the
'initialize_plugin" script, and still receiving the same error.
On the server, there is a
"plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a
"plugins/aspace-oauth/gems/gems/public_suffix-
Try updating the Gemfile.lock to use the 4.0.6 version of the gem and then
run the initialize_plugin script. I'm pretty sure that was how I got around
the issue at one point.
You just need to get the plugin bundled. Version does not matter (in my
experience).
Tom
On Tue, Dec 6, 2022 at 3:03 PM D
