Same here. AFAIK the unfiltered-mu plugin doesn't help during imports.
Core enhancement / plugin idea:
Default blog admin behavior:
During user initiated import, when the process encounters code that would be stripped out, it suspends the process and displays a dialog informing the user that due to security policies that data such as embeds and scripts will be lost during import. They then have the option of cancelling or continuing. If they continue, when import is complete the user is then given a manifest of what was stripped out. If they cancel, they have the option of requesting a manifest to see what needs to be changed pre-import.
This should give them a bit more opportunity to then edit the posts to add the features back in using Site Admin approved plugins.
Default site admin behavior:
During site admin initiated import, when the process encounters code that would be stripped out, it suspends the process and displays a dialog which provides the option to keep the content, strip the content, or cancel the import.
Site Admin options settings:
- Checkbox toggle to allow users to keep content during import.
- Checkbox toggle to email site admin when a user imports a site with potentially harmful code.
Additional core/plugin enhancements required:
Unfiltered-mu updated to NOT strip code when switching between visual and html editors.
Add site-admin menu.
- checkbox to select which roles are unfiltered
- text input to add usernames for user-specific unfiltered (similar to how site-admins are added)
---
Thoughts? I personally see these as core enhancements rather than plugins because of the amount of hooks necessary. Opinions on that? If so, thoughts on which Trac to request them in?