Invalid ODT generated when tokens contain XML reserved symbols
The Print/Merge feature creates broken ODT file using an ODT template with tokens if the data contains an ampersand (&). The
& character gets written directly to the
content.xml, therefore creating invalid XML, and therefore an invalid ODT.
- Create a contact with
Test & Testin Adressee.
- Create an ODT template containing
- Open the Print/Merge activity on the previously created contact.
- Select the previously created ODT as template.
- Perform the merge.
The resulting ODT file is broken.
A valid ODT file should be generated (eg. reserved XML symbols should be properly escaped).
- CiviCRM: 5.34.0
- PHP: 7.3
- CMS: Drupal 9.1