I've just finished cleaning up the data from an application I was using previously and have got everything into a few WXR files. As a final test, I just imported them back into a local test installation, and all Vimeo and YouTube oEmbeds are failing. (This presumably applies to any other oEmbed media; it just so happens those are the majority in this case) All that gets displayed is the video URLs as plain text.

The only way I've found to force the embeds to become functional is to manually republish the various posts, and it must be done via the full post edit screen. Quick Edit'ing and bulk editing on the listing screen has no effect. There are ~2000 of these posts, so this process is completely out of the question.

Is this a known problem? And, obviously, is there a way around it?
I can't find anything that matches this situation so far. Most support threads that seem close have to do with the import process stripping iframe/object embeds, not disabling oEmbeds. Others involve the oEmbed URLs not being recognized at all(read: the feature failing altogether), not in this specific context.

Alternately, what is the difference between publishing a post via quick/bulk editing and doing it on the full edit screen? (Why is there a difference?) And can that be hacked into the other process so I could at least do it that way?

Just confirmed the behavior on the live installation.
I don't expect there'll be anything interesting, but for reference a snippet of a couple of posts from one of the WXR files.

1 Answer 1


Maybe you can apply some content filters to ensure oEmbed will work. I applyed a simple regex in one of my themes because I know of some plugins that can break the oEmbed support. This can also work for you.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.