Support » Requests and Feedback » Stupid Limitation

  • When writing a post, I am unable to embed an iFrame object. For example, I’m trying to embed the following:

    <iframe src=’’ frameborder=’0′ width=’410′ height=’342′></iframe>

    WordPress 2.5 refuses to accept this. When I try to save the post, the iFrame disappears.

    This is really, really stupid. let’s me embed this exact same object. I don’t understand why Blogger can do something that WordPress can’t. Isn’t WordPress supposed to be superior???

Viewing 7 replies - 1 through 7 (of 7 total)
  • I’m afraid neither of these posts provide a workable solution. Moreover, I believe WP 2.5 has rendered any previous workaround impossible.

    There’s a suggestion that iFrames are not XHTML-compliant. That may be so, I don’t know, but it is unacceptable not to support iFrames, as major players such as Google still use iFrames for embedding web objects.

    I wonder if I should look for another blogging platform…


    Just for sh*ts and giggles I tried the code on one of my posts and it worked fine.

    Maybe you need this plugin.

    I wanted to embed Google maps as I had in the past, but the editor would strip the code, but I did find a stupid workaround. If you paste the code into the html view and save it before switching back to visual view the code stays in tact. If you switch views before saving it strips the code.

    This is a TinyMCE issue, it can be picky about that sort of thing.

    If you want to use HTML code, use the HTML editor. It won’t mess with your HTML code.

    Ok, this issue is really making me angry. I have searched and read literally HUNDREDS of posts regarding using iFrames. None seem to adress the issues that I am having. Frankly I’m worn out.

    I am using WordPress MU, which I gather is based on the latest code base 2.6.1.

    I have already set my user preference to use the code editor not the visual editor. When I add my iFrame code, the editor strips is out.

    What is the freaking solution to this problem?

    After having similar frustrations, I came across the wp-unformatted plugin. Basically you just add the key/value pair ‘sponge’=1 to any post, and the editor will not mess with the raw HTML. The downside (and not obvious from the documentation) is that you have to put all the <p> tags in the post yourself.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Stupid Limitation’ is closed to new replies.