date:20170921

Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend

2017-09-21 Thread Jason Loeffler

Are you making an external http request to an endpoint, resulting in the
log output above? Or are you somehow issuing the POST method internally?

What do you mean by "I simply clicked collections and then clicked on the
first one"?

Can you refer us to the other user report for this error?

On Thu, Sep 21, 2017 at 6:13 PM, Jones, Jeremy  wrote:

> I saw another person got this error but for a different request.  Any
> ideas on what can cause this is appreciated.
>
>
>
> thanks
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:
> archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of *Jones,
> Jeremy
> *Sent:* Wednesday, September 20, 2017 5:10 PM
> *To:* Archivesspace Users Group  lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] [EXT] Re: can't view
> collections on the backend
>
>
>
> This sender failed our fraud detection checks and may not
> be who they appear to be. Learn about spoofing
> 
>
> Feedback 
>
> Sure,  I think this is what the log captured:
>
>
>
> Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute
>
> INFO: [collection1] webapp= path=/select params={q=(id:("\/
> repositories\/3\/resources\/243\/tree\/root"))=
> \=true=0="=-exclude_by_
> default:true=publish:true=1=json=true} hits=0 status=0
> QTime=1
>
>
>
> Sep 20, 2017 4:39:37 PM 
> org.eclipse.jetty.server.handler.ContextHandler$Context
> log
>
> INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- :
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url:
> http://localhost:8089/search?publish=true_size=10=
> collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+%
> 28types%3Apui+AND+types%3Apui_container%29=1
>
>
>
> I simply clicked collections and then clicked on the first one.
> Repositories/3/resource/243.  I hope this helps.
>
>
>
> jeremy
>
>
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [
> mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org
> ] *On Behalf Of 
> *Donald
> Mennerich
> *Sent:* Wednesday, September 20, 2017 4:59 PM
> *To:* Archivesspace Users Group  lyralists.lyrasis.org>
> *Subject:* [EXT] Re: [Archivesspace_Users_Group] can't view collections
> on the backend
>
>
>
> Jeremy,
>
> Can you share the http requests you made to generate the error?
>
> Don
>
>
>
>
>
> On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy 
> wrote:
>
> Hello,
>
>
> I’m having a few issues with Archivesspace.  First, I cannot view the
> contents of a collection on the backend view (:8089).  I can view them on
> the front end and edit them.  But the backend view says (We're sorry, but
> something went wrong.
>
> If you are the application owner check the logs for more information.
>
>
>
> The logs say:
>
>
>
>
>
>
>
> Sep 20, 2017 4:39:38 PM 
> org.eclipse.jetty.server.handler.ContextHandler$Context
> log
>
> INFO: I, [2017-09-20T16:39:38.022275 #18373]  INFO -- :
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server
> Error in 507ms
>
>
>
> Sep 20, 2017 4:39:38 PM 
> org.eclipse.jetty.server.handler.ContextHandler$Context
> log
>
> INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- :
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e]
>
>
>
> Sep 20, 2017 4:39:38 PM 
> org.eclipse.jetty.server.handler.ContextHandler$Context
> log
>
> INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- :
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error
> (undefined method `[]' for nil:NilClass):
>
>
>
> Sep 20, 2017 4:39:38 PM 
> org.eclipse.jetty.server.handler.ContextHandler$Context
> log
>
> INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- :
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result &&
> @result.respond_to?(:metadata) %>
>
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2:
>
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3:  type="application/ld+json">
>
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 4: <%=
> JSON.pretty_generate(@result.metadata).html_safe %>
>
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 5: 
>
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %>
>
>
>
> Sep 20, 2017 4:39:38 PM 
> org.eclipse.jetty.server.handler.ContextHandler$Context
> log
>
> INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- :
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e]
>
>
>
> Sep 20, 2017 4:39:38 PM 
> org.eclipse.jetty.server.handler.ContextHandler$Context
> log
>
> INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- :
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in
> `metadata'
>
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 
> app/views/shared/_metadata.html.erb:4:in
> `_app_views_shared__metadata_html_erb__1424742346_2312'
>
> [7f48c48b-7c0a-4a31-9625-d88b32bb353e] 
> app/views/layouts/application.html.erb:19:in
>

Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend

2017-09-21 Thread Jones, Jeremy

I saw another person got this error but for a different request.  Any ideas on 
what can cause this is appreciated.

thanks

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Jones, Jeremy
Sent: Wednesday, September 20, 2017 5:10 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on 
the backend


This sender failed our fraud detection checks and may not be who they appear to 
be. Learn about spoofing

Feedback

Sure,  I think this is what the log captured:

Sep 20, 2017 4:39:37 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp= path=/select 
params={q=(id:("\/repositories\/3\/resources\/243\/tree\/root"))=\=true=0="=-exclude_by_default:true=publish:true=1=json=true}
 hits=0 status=0 QTime=1

Sep 20, 2017 4:39:37 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: D, [2017-09-20T16:39:37.564842 #18373] DEBUG -- : 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] POST Search url: 
http://localhost:8089/search?publish=true_size=10=collection_uri_u_sstr%3A%22%2Frepositories%2F3%2Fresources%2F243%22+AND+%28types%3Apui+AND+types%3Apui_container%29=1

I simply clicked collections and then clicked on the first one.  
Repositories/3/resource/243.  I hope this helps.

jeremy


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Donald Mennerich
Sent: Wednesday, September 20, 2017 4:59 PM
To: Archivesspace Users Group 
>
Subject: [EXT] Re: [Archivesspace_Users_Group] can't view collections on the 
backend

Jeremy,
Can you share the http requests you made to generate the error?
Don


On Wed, Sep 20, 2017 at 5:53 PM, Jones, Jeremy 
> wrote:
Hello,

I’m having a few issues with Archivesspace.  First, I cannot view the contents 
of a collection on the backend view (:8089).  I can view them on the front end 
and edit them.  But the backend view says (We're sorry, but something went 
wrong.
If you are the application owner check the logs for more information.

The logs say:



Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: I, [2017-09-20T16:39:38.022275 #18373]  INFO -- : 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] Completed 500 Internal Server Error in 
507ms

Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-20T16:39:38.041159 #18373] FATAL -- : 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e]

Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-20T16:39:38.041735 #18373] FATAL -- : 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] ActionView::Template::Error (undefined 
method `[]' for nil:NilClass):

Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-20T16:39:38.043402 #18373] FATAL -- : 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] 1: <% if @result && 
@result.respond_to?(:metadata) %>
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] 2:
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] 3: 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] 4: <%= 
JSON.pretty_generate(@result.metadata).html_safe %>
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] 5: 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] 6: <% end %>

Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-20T16:39:38.043859 #18373] FATAL -- : 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e]

Sep 20, 2017 4:39:38 PM org.eclipse.jetty.server.handler.ContextHandler$Context 
log
INFO: F, [2017-09-20T16:39:38.044331 #18373] FATAL -- : 
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/models/resource.rb:101:in `metadata'
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] app/views/shared/_metadata.html.erb:4:in 
`_app_views_shared__metadata_html_erb__1424742346_2312'
[7f48c48b-7c0a-4a31-9625-d88b32bb353e] 
app/views/layouts/application.html.erb:19:in 
`_app_views_layouts_application_html_erb___1292011715_2310'

I cannot make much from this log entry other than there was a fatal error.  Any 
ideas what could be causing this?

Thank you
jeremy

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

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

2017-09-21 Thread Kevin Clair

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-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@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
Your Details
Name: m
Email: mark.cus...@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-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Kevin Clair
Sent: Thursday, 21 September, 2017 5:15 PM
To: Archivesspace Users Group 
>
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 #<#: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:   Record Requested

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

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

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

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

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

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

Sep 21, 2017 3:08:09 PM

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

2017-09-21 Thread Custer, Mark

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
Your Details
Name: m
Email: mark.cus...@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-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Kevin Clair
Sent: Thursday, 21 September, 2017 5:15 PM
To: Archivesspace Users Group 
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 #<#: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:   Record Requested

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

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

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

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

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

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





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:

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

2017-09-21 Thread 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 #<#: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:   Record Requested
[5c583ccc-1669-40c4-9f90-81f09fac562b] 5:   Title: <%= 
@request.title %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 6:   <% url = 
"#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}" %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 7:   URL: <%= 
link_to url, app_prefix(url) %>
[5c583ccc-1669-40c4-9f90-81f09fac562b] 8: 
[5c583ccc-1669-40c4-9f90-81f09fac562b] 9: 
[5c583ccc-1669-40c4-9f90-81f09fac562b]10: 

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-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Tang, Lydia
Sent: Thursday, September 21, 2017 1:19 PM
To: 'archivesspace_users_group@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@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Advice on Custom Theming

2017-09-21 Thread Majewski, Steven Dennis (sdm7g)


I believe you are running into Rails defaults before the ASpace plugins come 
into play.


As I test, I added the line  'layout "custom"' to 
frontend/app/controllers/application_controller.rb.

It will then use layouts/custom.html.erb, and that layout appears  to work if 
that file is in either frontend/app/views/layouts/  or  
plugins/local/frontend/views/layouts/ .


However, If I try moving the edited copy of application_controller.rb to the 
plugins/local/frontend/controllers/ directory, it no longer works as the 
default application controller is what the base class for all other 
controllers. Perhaps making the plugins extensible on this level would require 
adding a conditional check for plugin layouts in base application_controller .



Instead of deep mods, another possible way is patching it after the fact with 
javascript.

You could try adding something like the following  to 
plugins/local/frontend/views/layout_head.html.erb:




  $( function() {
  
$('.container-fluid').removeClass('container-fluid').addClass('container');
  });




-- Steve Majewski / UVA Alderman Library

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Chelsea 
Lobdell 
Sent: Thursday, September 21, 2017 1:04:40 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Advice on Custom Theming

Hi Archivesspace,

I'm looking for some advice on how to get started with custom theming. I've 
been reviewing this custom theming documentation:
https://github.com/archivesspace/archivesspace/blob/master/CUSTOMIZING_THEMING.md
[https://avatars0.githubusercontent.com/u/1311559?v=4=400]

archivesspace/CUSTOMIZING_THEMING.md at master 
...
github.com
Customizing and Theming ArchivesSpace I just want to change some of the labels 
and messages! All the messages and labels are stored in locales files, which is 
part of ...




The initial change I'm trying to make is really simple. In 
layouts/application.html.erb I just need to change the header, navigation and 
maincontent from container-fluid to container to match the style of the other 
applications in our application suite.

My first attempt was to add 
archivesspace/plugins/local/frontend/views/layouts/application.html.erb and to 
make the appropriate changes. However, after a restart I am not seeing my 
changes. Can anyone advise me on how to get this working?

I also recognize that application.html.erb is a pretty important file to be 
customizing. If anybody has advice on how best to approach this, I would 
appreciate it.

- Chelsea
---
Chelsea Lobdell
Library Web Developer/ Swarthmore College
clobd...@swarthmore.edu / (610)690-6818
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface

2017-09-21 Thread Benn Joseph

Hi all,

We've encountered an issue with the v2.1.2 Print-to-PDF button in the public 
interface--apparently for any resource record with an ampersand that is 
followed immediately by another character that is not a space (e.g. "b" or 
"AT"), the ampersand is misinterpreted and causes the Print-to-PDF button to 
fail with an error. For me, that error is just "something went wrong", but the 
log shows this (when it gets tripped up on "b"):



RuntimeError (Failed to clean XML: The reference to entity "w" must end with 
the ';' delimiter.):



So we're guessing ArchivesSpace is thinking "" should be "", and so forth 
for any other string of text with an ampersand. I checked this by going into a 
record that wouldn't print and changing the lone suspect ampersand ("AT" to 
"AT and T") and the PDF generated just fine.



This doesn't impact being able to just view resource records in the public 
interface, it's just the PDF function that isn't working. It's a problem, 
though, because we want to be able to use that PDF functionality but we also 
have a lot of ampersands in our resource records! Has anyone else experienced 
this issue or possibly come up with a fix?



Thanks,

--Benn

Benn Joseph
Head of Archival Processing
Northwestern University Libraries
Northwestern University
www.library.northwestern.edu
benn.jos...@northwestern.edu
847.467.6581

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Advice on Custom Theming

2017-09-21 Thread Chelsea Lobdell

Hi Archivesspace,

I'm looking for some advice on how to get started with custom theming. I've
been reviewing this custom theming documentation:
https://github.com/archivesspace/archivesspace/blob/master/CUSTOMIZING_THEMING.md

The initial change I'm trying to make is really simple. In
layouts/application.html.erb I just need to change the header, navigation
and maincontent from container-fluid to container to match the style of the
other applications in our application suite.

My first attempt was to add
archivesspace/plugins/local/frontend/views/layouts/application.html.erb and
to make the appropriate changes. However, after a restart I am not seeing
my changes. Can anyone advise me on how to get this working?

I also recognize that application.html.erb is a pretty important file to be
customizing. If anybody has advice on how best to approach this, I would
appreciate it.

- Chelsea
*---*
*Chelsea Lobdell*
*Library Web Developer/ Swarthmore College*
*clobd...@swarthmore.edu  / (610)690-6818*
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Top container record corrupted

2017-09-21 Thread George Stanley Kozak

Hi, Everyone:

Recently, one of our Archivists created a top container record attached to an 
archival object in ASpace.

She then changed the access restriction on the archival object but deleted a 
sub-note field it expected to have. This gave her the following error: "Sub 
Notes - translation missing: 
en.validation_errors.must_contain_at_least_one_subnote".

We believe that this corrupted the top container record. When she tried to 
create a new top container record attached to the same archival object, it was 
created, but when trying to view the container the "We're sorry, something went 
wrong"  error occurred.

I tried to go through the logs to find what exactly happened, but I am having 
trouble pinpointing  where the error occurred in the logs.
Has anyone else experienced something similar or has any hints to give us as to 
what we can do to fix this problem?
Thanks!

George Kozak
Digital Library Specialist
Cornell University Library Information Technologies (CUL-IT)
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend

Re: [Archivesspace_Users_Group] [EXT] Re: can't view collections on the backend

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

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

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

Re: [Archivesspace_Users_Group] Advice on Custom Theming

[Archivesspace_Users_Group] ampersand issue with PDF button in 2.1.2 public interface

[Archivesspace_Users_Group] Advice on Custom Theming

[Archivesspace_Users_Group] Top container record corrupted

9 matches

Site Navigation

Mail list logo

Footer information