Tom,
Thanks for the suggestion. If I understand you correctly, the suggestion is
to modify the "Gemfile.lock" file on the "aspace-oauth" gem to change the
"public_suffix" version to 4.0.6.
I gave it a try, and made the following changes to the "Gemfile.lock" file
(and reran the "initialize-plugi
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
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-
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,
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
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
