Ticket #6807 (closed defect (bug): duplicate)

Opened 4 years ago

Last modified 3 years ago

Unable to embed iFrame objects in visual view

Reported by: richardeng2008 Owned by: anonymous
Priority: normal Milestone:
Component: TinyMCE Version: 2.5.1
Severity: normal Keywords:
Cc:

Description

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

<iframe src=' http://docs.google.com/EmbedSlideshow?docid=dgdvf97f_18cv5mmfdd' 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. Blogger.com 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???

Change History

  • Milestone changed from 2.7 to 2.5.1

Replying to richardeng2008:

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

<iframe src=' http://docs.google.com/EmbedSlideshow?docid=dgdvf97f_18cv5mmfdd' 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. Blogger.com 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???

  • Priority changed from high to normal
  • Version changed from 2.5 to 2.5.1
  • Component changed from General to TinyMCE
  • Severity changed from major to normal
  • Summary changed from Unable to embed iFrame objects to Unable to embed iFrame objects in visual view

This seems to be related -- if you successfully add an iframe object, working in HTML view, and later anyone touches/enters edit on the post (which of course defaults to visual editor) than the entire iframe is removed, without notice.

For a multi-author blog like ours, which uses iframes to include flash slideshows, this often results in the accidental and un-notified loss of huge quantities of content, though I'm sure most people won't run into this particular problem. (i.e. I think this is a pretty severe bug, but I'm not going to attempt to change the severity from the normal checked above.)

comment:4   ryan4 years ago

  • Milestone changed from 2.5.2 to 2.9

Milestone 2.5.2 deleted

  • Status changed from new to closed
  • Resolution set to duplicate
  • Milestone 2.9 deleted

see #9874

Note: See TracTickets for help on using tickets.