# Import XML stripping embedded content

**URL:** <https://pressbooks.community/t/import-xml-stripping-embedded-content/423>\
**Category:** Developer Questions\
**Created:** [March 12, 2018, 9:39pm UTC](https://pressbooks.community/t/import-xml-stripping-embedded-content/423 "2018-03-12T21:39:03Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ned](https://pressbooks.community/user_avatar/pressbooks.community/ned/32/533_2.png) [@ned](https://pressbooks.community/u/ned)\
**Post date:** [March 13, 2018, 1:02pm UTC](https://pressbooks.community/t/import-xml-stripping-embedded-content/423/6 "2018-03-13T13:02:04Z")

</div>

Hi @bryan, in talking through this with @dac.chartrand I think our preference would be to follow the WordPress approach, where in a multisite context only super admins (who have the `unfiltered_html()` capability) can bypass sanitization routines when creating/saving posts. Would this work for your use case? It would mean that super admins could import from WordPress XML files that contain iframes without issue, but other users would still be subject to the sanitizing that is applied in all other contexts. This would make the behaviour consistent. What are your thoughts?

---

_[View the full topic](https://pressbooks.community/t/import-xml-stripping-embedded-content/423)._