Where a field for export contains valid xml, or is pushed through a field formatter that outputs valid xml, it would be nice to be able to exclude that field from xml encoding.
Add a new option to the views data export plugin for xml that allows you to specify fields that will be excluded from xml encoding. That way, if a user chooses a field formatter that already outputs valid xml, they can then exclude that field from xml encoding too.
User interface changes
The new "Exclude these fields from XML Entity Encoding" options can be added as checkboxes to the Style Options for the Views data export XML style plugin.
Original report by adam_b
I have a database which includes a lot of useful info in field-collection entities. When I try and export this in XML format, it's output as a table with escaped HTML tags, no matter what format I choose for the field (see attachment).
Is this an issue for this module, or for the field-collection module? Are there any alternatives? I can see ways to handle this, but ideally I'd like a full XML structure.
|#22||views_data_export-1446102-xml-encoding.patch||3.95 KB||Steven Jones|
|#19||views_data_export-1446102-disable-xml-encoding.patch||6.46 KB||Steven Jones|
PASSED: [[SimpleTest]]: [MySQL] 84 pass(es).
|#17||views_data_export-1446102-disable-xml-encoding.patch||4.08 KB||Steven Jones|
FAILED: [[SimpleTest]]: [MySQL] 81 pass(es), 0 fail(s), and 6 exception(s).
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch views_data_export-disable_xml_encoding-1446102-6.patch. Unable to apply patch. See the log in the details link for more information.