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

[Kevin Clair]

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}" %>
[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] 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