[Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

Tue Oct 24 14:27:52 EDT 2017

Hi Donnelly,

These settings are controlled by options in the config.rb file on your ArchivesSpace server. A bug and some improvements with the email requesting feature on the PUI were resolved in version 2.2.0, so if you upgrade to that version, if should work correctly. An improvement that was made for 2.2.0 was that if you have a contact email address in a repository record, it can be used as the email address for requests (https://github.com/archivesspace/archivesspace/pull/979) rather than having to specify an email address separately. You will still need to enable the requesting feature and associated settings in the config file, however.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Walton, Donnelly
Sent: Monday, October 23, 2017 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We have recently upgraded to 2.1.2 and are doing a soft launch of the PUI.  Where do we go to setup the feature and tell the system where to send the emails?

Many thanks,
Donnelly

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
[The University of Alabama]<https://www.ua.edu/>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, September 21, 2017 4:39 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We’ve been able to receive the e-mail confirmations ArchivesSpace sends, both with my personal e-mail and with LibAnswers. It’s only when it tries to render request_received_email.html that it throws the error.  -k

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Thursday, September 21, 2017 3:31 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

All,

I wish that I could offer technical advice on how to get things set up, but unfortunately I'm of no use in this case.  I do know that this feature used to be configured on our Test Corpus site, though, and that it functioned as expected at that time.

Here's what a message would look like that's sent to a patron (as you can see, it doesn’t include ALL of the data, like what the staff would receive), and they shouldn’t see an error message when requesting after everything has been configured to allow email requesting:

Thank you for your request
Record Requested
Title: Watercolor of Brassie fly nymph (fishing fly)
URL: http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375<https://urldefense.proofpoint.com/v2/url?u=http-3A__aspace.hudmol.com-3A7310_repositories_14_digital-5Fobjects_4375&d=DwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=hES0nr_7CQRdsaxxcbpbcujfoSJVVVtSbikTnQDfBMQ&s=fEcKFYM5n4pdR51TDuNa_20WsC4Rr2r-cKOf4FBNyuk&e=>
Your Details
Name: m
Email: mark.custer at yale.edu<mailto:mark.custer at yale.edu>
Date:
Notes for Staff:

I don’t believe that the email that was sent to staff ever had a specialized template, like this one, however.  It was just meant to be a proof of concept showing how all of the request data could be sent in an email message in order to fulfill the user story about allowing researchers to make requests directly from the PUI.

Hopefully others will be able to weigh in soon with more detailed instructions how to get this configured properly.  I seem to remember that with the Gmail account that we used for testing, Gmail had to be told to allow the use of unsecured apps (though I’m not sure why exactly that was or might be).

Just so that I’m clear, though… Lydia, Kevin: it sounds like you have it configured to receive emails okay, but the emails to whomever requested the material is not being sent/received.  Is that correct?

Mark

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, 21 September, 2017 5:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs:

INFO: I, [2017-09-21T15:08:03.838360 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600

[the e-mail successfully sends here; log output omitted]

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: I, [2017-09-21T15:08:09.740133 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#<Class:0x46d13c0a>:0x59036603>):

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]     4:   <h2>Record Requested</h2>

[5c583ccc-1669-40c4-9f90-81f09fac562b]     5:   <strong>Title</strong>: <%= @request.title %><br>

[5c583ccc-1669-40c4-9f90-81f09fac562b]     6:   <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}<mailto:%7d#{@request.request_uri}>" %>

[5c583ccc-1669-40c4-9f90-81f09fac562b]     7:   <strong>URL</strong>: <%= link_to url, app_prefix(url) %>

[5c583ccc-1669-40c4-9f90-81f09fac562b]     8: </div>

[5c583ccc-1669-40c4-9f90-81f09fac562b]     9:

[5c583ccc-1669-40c4-9f90-81f09fac562b]    10: <div class="user">

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]

Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log

INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378'

[5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email'

[5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request'

-k

-----Original Message-----

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia

Sent: Thursday, September 21, 2017 1:19 PM

To: 'archivesspace_users_group at lyralists.lyrasis.org'

Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

Hello, we recently upgraded from 2.1.1 from 1.5.3.  With our users taking advantage of the request feature through our PUI, they have received this “We’re sorry something went wrong” message after submitting their request.  Is this normal?  Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI?

Thanks!

Lydia

_______________________________________________

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=yCOvlNmPPowIK_FHWplCUKa3UJhEsCZ5AWPTGq2qjMk&s=blzfAbR70wCLQrOIDae9pDrRNAZ_79j4aYMufxVfe2w&e=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/4cc6fcbf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.gif
Type: image/gif
Size: 6052 bytes
Desc: image004.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/4cc6fcbf/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/4cc6fcbf/attachment.jpg>