Bug #8553
EAD export fails when subject access points have ampersands in the name
Status: | Verified | Start date: | 06/11/2015 | |
---|---|---|---|---|
Priority: | Medium | Due date: | ||
Assignee: | Dan Gillean | % Done: | 0% | |
Category: | EAD | |||
Target version: | Release 2.2.0 | |||
Google Code Legacy ID: | Tested version: | 2.2, 2.3 | ||
Sponsored: | No | Requires documentation: |
Description
To reproduce: Create a subject access point in an archival description with an ampersand in it, e.g. http://qa-22x.test.artefactual.com/flora-roy-fonds
Result: An error is displayed:
_"This page contains the following errors:
error on line 2 at column 1: Extra content at the end of the document
Below is a rendering of the page up to the first error."_
Expected result: an EAD file to be generated successfully.
History
#2 Updated by Mike Gale almost 7 years ago
- File 0001-Only-pass-strings-to-esc_specialchars-8553.patch
added
- Status changed from New to Code Review
- Assignee changed from Mike Gale to Mike Cantelon
#3 Updated by Mike Cantelon almost 7 years ago
- Status changed from Code Review to Feedback
- Assignee changed from Mike Cantelon to Mike Gale
Looks good to me!
#4 Updated by Mike Gale almost 7 years ago
- Status changed from Feedback to QA/Review
- Assignee changed from Mike Gale to Dan Gillean
#5 Updated by Mike Gale almost 7 years ago
merged in qa/2.2.x 283a45d238a6a309e497bc888ab5ef639d1607b6
#6 Updated by Dan Gillean almost 7 years ago
- Status changed from QA/Review to Verified
Added place, name (subject), and subject access points with ampersands. Managed to export, and reimport without issue, including display issues on rountrip. Lookin' good!