Thanks for providing detailed context about how specific versions of AS have
handled XML, Andrew. We are currently running 2.8.1. Yes, I would like to try
your fix.* I would like to install it on our development instance and see what
happens. When you have a moment, please let me know how I
My fix should prevent all "Failed to clean XML: The reference to
entity..." errors triggered by EAD-compliant encoding. But, depending on
what version of ArchivesSpace you are running, it may only make a
difference in niche cases. As I understand it (although Blake may wish
to correct me if I
Andrew, thank you for taking the time to point me to your Github fix. I do see
the "Failed to clean XML" error in my logs, but in each case it is seemingly
upset about missing semicolons: "Failed to clean XML: The reference to entity
"W" must end with the ';' delimiter."
If I understand your
Kyle Breneman wrote on 2022-01-05 17:36:41:
> Thank you for that reminder, Blake! Another question: the print action was
> being run from the following pages. Wouldn't clicking the AS print button
> itself register in the logs? If so, how could I efficiently find those
> lines?
>
>
If you do see that "Failed to clean XML" message in the logs, then you
might be interested in this pull request I submitted recently:
https://github.com/archivesspace/archivesspace/pull/2553
I could put the same fix into the form of a plug-in, if that is what you
are seeing, you have the
We had a similar problem a month ago which was caused by mixed protocols
(http/https). We resolved it by forcing all traffic to use https.
-Lyman
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Kyle
Breneman
Sent: Wednesday, January 05, 2022 12:29 PM
To:
Thank you for that reminder, Blake! Another question: the print action was
being run from the following pages. Wouldn't clicking the AS print button
itself register in the logs? If so, how could I efficiently find those lines?
https://archivesspace.ubalt.edu/repositories/2/resources/92
Our archives staff have noticed that AS tends to get hung up when users click
the Print button on some of our largest collections. Campus IT tested this
today. The server did not hang for them, but the print action also did not
complete. They got a very, very generic error message
