I just upgraded to 6.x-2.3.
When I attempt to edit a page with a flash animation on the page the page does not load properly into the editor. Everything past the animation is lost and the animation is duplicated. If I don't save my page remains ok. I need to do more testing to understanding this problem, but just getting a discussion started.
When I originally put the flash object into the page I did not use a button from FCKeditor, I instead switched to source mode and just typed in all the HTML and object code needed and it worked fine. Is it possible that this later release of wysiwyg requires that the flash be added through the FCKeditor flash button?
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | homepage.txt | 4.94 KB | webservant316 |
Comments
Comment #1
webservant316 commentedcorrected title and change to major
Comment #2
twodWhich browser(s) are you using?
Is it the same in all of them?
Are you sure the markup is valid to begin with? (Even the smallest piece of invalid markup can really mess things up in WYSIWYG mode).
If you want to check the markup without having the editor touch it as soon as the page loads, either set the editor to be disabled by default or disable JavaScript before editing the node, check the markup, correct any mistakes, save and re-activate the editor/JavaScript.
Wysiwyg itself doesn't care much about what's in the content and will not actively modify it.
It's more likely that the editor isn't capable of representing the markup needed for the Flash animation without the Flash plugin being active. That plugin is responsible both for inserting a placeholder where the animation's located in WYSIWYG mode and making sure the browser itself (IE) doesn't remove the tags it doesn't understand.
It's possible that the Teaser Break plugin could be messing with the source if you have it active. It gets the generated source as a string from the editor, converts it to a DOM to find/replace its own placeholders and then converts it back to a string for output. During this process, in which the conversions are done by the browser, the browser might strip out markup it thinks is broken.
Comment #3
webservant316 commentedMore info... Editing the page works with Firefox 3.6.13, but doesn't with IE8. I didn't noticed it before because I always use Firefox to edit these days, but over the weekend used IE without noticing it.
How would I determine if the markup itself is bad, or it is something else. I've only noticed the problem on two pages and on those pages I have hand coded a flash object. I attached the HTML markup if you can take a quick look for a problem that would cause this.
Comment #4
webservant316 commentedchange title again...
Comment #5
webservant316 commented@TwoD - any further thoughts? Have enough info?
Comment #6
twodI completely lost track of this issue, I'm sorry for that.
You can check the validity of the HTML using a tool like http://validator.w3.org/ or http://infohound.net/tidy/tidy.pl.
I pasted the markup into the second tool to make it more readable (it also adds a few wrapping tags because it wasn't a complete document, but ignore those.). It noted that some
<strong></strong>tags were nested near the beginning, which isn't allowed. It also complained about the embed tag not being valid, but IE understands it so that's not a big thing.When I opened the text file I also noticed a couple of strange characters, like
wmode="�transparent�".Perhaps the place you copied the snipped from had "smart quotes" turned on? The browser might indeed have misinterpreted this code, as the flash/media plugins are designed to take care of some cross-browser issues related to special markup needed for things like Flash, and the tendency of them being mangled by the browser. Also, our own Teaser Break plugin doesn't improve the situation by passing the contents via the browser again after the editor has fixed it...
Sorry again for extreme delay.
I'll close this issue for now. Feel free to reopen it again.
Comment #7
webservant316 commentedthanks