Issues
- PUI: ampersands in notes lead to "Failed to clean XML" error when printing to PDFANW-831Resolved issue: ANW-831Blake Carver
- Capitalize "Creator" as the default <origination> LABEL value.ANW-777Resolved issue: ANW-777Adam Jazairi
- Duplicate Record Type Filter in Search ResultsANW-749Resolved issue: ANW-749Sarah Morrissey
- As an archivist, I would like to record multiple Language entries using controlled terms.ANW-697Resolved issue: ANW-697Lora Woodford
- Date type "Range" should not appear for Deaccession DatesANW-684Resolved issue: ANW-684Sarah Morrissey
- EAD export validation issue: attributes for linking tags (e.g., HREF in <extref>) aren't pre-pended with xlink namespaceANW-669Resolved issue: ANW-669
- Add and revise fields and sub-records for the Agents module as per the community-authored specificationANW-661Resolved issue: ANW-661Manny Rodriguez
- As a repository manager or archivist, I want some of the terminology in the Background Jobs area to be changed to make the functionality clearer to usersANW-657Resolved issue: ANW-657Sarah Morrissey
- The RDE disappears and data is lost if a user (intentionally or unintentionally) clicks outside the RDE windowANW-391Resolved issue: ANW-391Lora Woodford
- As an archivist, I would like to record finding aid Language of Description using controlled valuesANW-382Resolved issue: ANW-382Lora Woodford
- HTML tags are inappropriately generated from the HTML to PDF process for the PUI, but only at the Collection Inventory level.ANW-269Resolved issue: ANW-269Tim DiLauro
- handling orphaned recordsANW-220Resolved issue: ANW-220Lora Woodford
- Physdesc/dimensions/physfacet note label values are not included in EAD exportsANW-150Resolved issue: ANW-150Manny Rodriguez
- As an archivist, I'd like Print-to-PDF to require fewer stepsANW-142Resolved issue: ANW-142Sarah Morrissey
- As a system administrator, I want to allow the "at" symbol (@) in usernamesANW-92Resolved issue: ANW-92Sarah Morrissey
- Reports user navigation needs streamliningANW-81Resolved issue: ANW-81Sarah Morrissey
- The system shall use ARK values in all OAI-PMH exports for URI references back to an ArchivesSpace instance.ANW-60Resolved issue: ANW-60Manny Rodriguez
17 of 17
PUI: ampersands in notes lead to "Failed to clean XML" error when printing to PDF
Done
Description
Environment
None
Details
Assignee
Blake CarverBlake CarverReporter
Blake CarverBlake CarverPriority
MajorHarvest Time Tracking
Open Harvest Time Tracking
Details
Details
Assignee
Blake Carver
Blake CarverReporter
Blake Carver
Blake CarverPriority
MajorHarvest Time Tracking
Open Harvest Time Tracking
Created January 8, 2019 at 7:36 PM
Updated September 25, 2019 at 2:38 PM
Resolved September 25, 2019 at 2:38 PM
Activity
Show:
Jared CampbellMarch 11, 2019 at 8:09 PM
I was able to & by using & and "&" by myself. From Josh's comment it seems like it may also be possible to enter an & using & as well? Tested in test.archivesspace.org
Joshua ShawMarch 5, 2019 at 7:02 PMEdited
This appears to still be an issue. Adding a note with the text "&ersand" in the staff UI yields a PUI note display of "&ersand". Tested in test.archivesspace.org
A single & character causes failures like this:
RuntimeError (Failed to clean XML: The reference to entity "ix" must end with the ';' delimiter.):
In a note field there is a link with a URL as follows:
http://example.com/something=FA000988536&ix=whatever&I=0&V=D&pm=1
It's choking on the &ix=whatever.
Or any string with an ampersand like J&J or W&S and so on...
This bug fix (which looks to be in the 2.5.1 release) looks to be for a similar issue involving ampersands: https://github.com/archivesspace/archivesspace/issues/972