Exporting fields that already output valid xml encoded content

struggling with the same problem myself.

http://drupal.org/node/1175082

I don't really understand jpcurley25 answer.
I have the same kind of issue: i'd like to export an xml that would look like:
nodes
-node
--title
--medias
---media
----title
----file

Any idea on how to do this?

What I did was modify the xml export template (views-data-export-xml-body--myview-name--mydisplay-name.tpl.php) to insert another view inside my current view:

<?php foreach ($themed_rows as $count => $row): ?>
  <point_info>
<?php foreach ($row as $field => $content): ?>
	<?php if ($field == 'field_medias'): ?>
	<?php 
		$view_name = 'xml_medias';
         $display_id = 'views-data-export';
		$myargs = $row['nid'];
		print views_embed_view($view_name,$display_id,$myargs);
	?>
	<?php else : ?>
		<?php if (trim($content)!='' && $xml_tag[$field]!='') : ?>
		    <<?php print $xml_tag[$field]; ?>><?php print $content; ?></<?php print $xml_tag[$field]; ?>>
		<?php endif; ?>
	<?php endif; ?>
<?php endforeach; ?>
  </point_info>
<?php endforeach; ?>

Hope this help someone.

Patch motivation

In my situation, I've written a field formatter that returns a render array that in turn outputs valid xml encoded content. When I apply this field formatter to my field for export, I want to be able to exclude the field from xml encoding by views_data_export_plugin_style_export_xml

Patch Solution

This patch adds checkboxes to views_data_export_plugin_style_export_xml::options_form(), where you can choose individual fields for exemption from xml entity encoding. Then, during the theme preprocessing in template_preprocess_views_data_export_xml_body() we check this setting before xml encoding each fields contents for inclusion in $themed_rows.

After applying the patch:

1. Set-up a new view for export,
2. Choose the Views Data Export - XML file format,
3. Choose some fields for export,
4. Edit the XML file Settings to choose which fields to exclude from XML entity encoding
5. Click Update preview to see the changes

.

#5 this looks great, but I can't get it to work. Where does this file need to go?

I've my view name is
"Text and Media XML"
and the Display name is:
"Data export"

I've named my template file:
views-data-export-xml-body--text-and-media-xml--data-export.tpl.php
also tried:
views-data-export-xml-body--text_and_media_xml--data_export.tpl.php

is that right?

I put it in the same directory as the original views-data-export-xml-body.tpl.php ,

but the override isn't happening.
maybe there's something dumb I'm missing?

thanks.

@donundeen : the file goes in your theme like other template files. Are you sure your views name and display name are correct? -> look at your views 'advanced' group + Other + System Name (sorry I'm translating from french I'm not sure of the terms). For info, my files are named:
views-data-export-xml-body--xml-panos.tpl.php
views-data-export-xml-footer--xml-panos--views-data-export_1.tpl.php
views-data-export-xml-header--xml-panos--views-data-export_1.tpl.php
views-data-export-xml-body--xml-panos--views-data-export-1.tpl.php
views-data-export-xml-footer--xml-panos--views-data-export_2.tpl.php
views-data-export-xml-header--xml-panos--views-data-export_2.tpl.php
views-data-export-xml-body--xml-pi.tpl.php
views-data-export-xml-footer--xml-pi.tpl.php
views-data-export-xml-header--xml-pi.tpl.php
views-data-export-xml-footer--xml-panos.tpl.php
views-data-export-xml-header--xml-panos.tpl.php
views-view-field--xml-pi--field-video2.tpl.php

@donundeen: you can look at 'advanced' + Other + Theme Information to get the list of template files you can use.

Thank you for the patch in #6. It's very useful and I'd love to see it committed.

In my case I needed to wrap a field in an additional tag. The patch allows me to create a template in my theme and simply wrap the output like this:
<mytag><?php print $output; ?></mytag>

Patch #6 works great for me as well. Thank you!
I needed it to embed a sub-view that already outputs some valid XML.

Patch #6 works perfectly for me too.

#6 worked for me as well; thanks for the patch!

#6: views_data_export-disable_xml_encoding-1446102-6.patch queued for re-testing.

This need some tests too.

Here's a re-roll for the test bot, still need to add tests.

How about this one. Fixes the notice and adds a test.

Thanks for the hard work everyone!

Committed to 7.x-3.x.

Here's a simple patch, that needs some work because the Views API changed from 3 -> 2.

Which patch can I use for drupal 6 version?

Thanks for your works.

I would know if there's a way to add custom tag to the field using "Rewrite the output of this field".
I've tried to add

<foo>[field_token]</foo>

but tags are been removed in the export

Add new summary outlining proposed solution.

just for reference and our make file, attached is a patch against views_data_export 3.0-beta6 that includes the committed patch #20 and adapts it for xml exports

As Drupal 6 nears the end of its life and support period, the 6.x version of Views Data Export will not be supported either. To that end, this issue has been closed, and will not be resolved in the 6.x branch of Views Data Export.

If this issue is still relevant to 7.x branch of Views Data Export, then please re-open and move to a relevant 7.x version.