[Archivesspace_Users_Group] incompatible encodings error on the v2.2.2 public site

[Kevin Clair]

Hello,

We upgraded to version 2.2.2 last night, and since then we've received the following error message when attempting to view some collections in the PUI:

Jan 18, 2018 9:25:21 AM org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: F, [2018-01-18T09:25:21.858975 #8903] FATAL -- : [d38ccd85-ec57-45c7-a749-aed7fd4f64d5] ActionView::Template::Error (incompat
ible encodings: UTF-8 and ASCII-8BIT):

Jan 18, 2018 9:25:21 AM org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: F, [2018-01-18T09:25:21.859788 #8903] FATAL -- : [d38ccd85-ec57-45c7-a749-aed7fd4f64d5]     38:   <section id="content" class
="container-fluid">
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5]     39:          <a name="maincontent" id="maincontent"></a>
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5]     40:          <%= flash_messages %>
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5]     41:          <%= yield %>
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5]     42:  </section>
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5]     43:
[d38ccd85-ec57-45c7-a749-aed7fd4f64d5]     44:  <script  type="text/javascript" >

I wrote a quick script to get the HTTP status codes for all of our collections in the PUI, and only 25 (out of 995) returned code 500, so this affects a small percentage of our collections and makes me think it might be an issue with our metadata or with the default character set in our database. I can confirm it's not an issue if I roll back to the previous release.

I think we'll have to go back to 2.2.1 while we resolve this, but I was curious if anyone else had encountered it and if they had taken any steps to resolve it that I should be aware of.

thanks!  -k
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180118/52940d12/attachment.html>