embedding video code
Posted: Sat Aug 14, 2010 5:28 pm
As a blog that does video embedding as a way of life now for some years, I have experienced many code issues, to say the least.
The biggest of which is that WYSWYG editors alter most JS code after that first SAVE. We are OKAY if we do not SAVE it again, or TWICE. Video content companies like YOUTUBE and Comedy Central somehow compensate for this problem, and even though you can see the code has changed it still works, though you will never get a W3 rating!
What most often happens is the last </embed> gets stripped which cause IE to go bonkers. This is presently the case with MSNBC which recently changed their embed code from the old simple <iFrame> To <object><embed>
If any of my writers who all use WYSWYG SAVE as a draft or go back later to edit and save again, the changed code does very bad things to our visitors who use IE. One can only save ONCE, that first time without it going bad.
I searched the issue recently and found it to be a rather big issue over at WORDPRESS, they have a plugin that uses the words "custom fields" and "value fields" which fixes the problem. I assume it holds the JS code inside a field box without disrupting it. One then puts "fieldbox1" or something in the editor where it slaps it in and it doesnt make a mess of things.
So out of the box so to say, can this work with our CUSTOM FIELDS down there, and how exactly is that done. Easily for Dummies!
This is also an issue with Adsense. If you save a nugget with it in TWICE it often goes bad.
The biggest of which is that WYSWYG editors alter most JS code after that first SAVE. We are OKAY if we do not SAVE it again, or TWICE. Video content companies like YOUTUBE and Comedy Central somehow compensate for this problem, and even though you can see the code has changed it still works, though you will never get a W3 rating!
What most often happens is the last </embed> gets stripped which cause IE to go bonkers. This is presently the case with MSNBC which recently changed their embed code from the old simple <iFrame> To <object><embed>
If any of my writers who all use WYSWYG SAVE as a draft or go back later to edit and save again, the changed code does very bad things to our visitors who use IE. One can only save ONCE, that first time without it going bad.
I searched the issue recently and found it to be a rather big issue over at WORDPRESS, they have a plugin that uses the words "custom fields" and "value fields" which fixes the problem. I assume it holds the JS code inside a field box without disrupting it. One then puts "fieldbox1" or something in the editor where it slaps it in and it doesnt make a mess of things.
So out of the box so to say, can this work with our CUSTOM FIELDS down there, and how exactly is that done. Easily for Dummies!
This is also an issue with Adsense. If you save a nugget with it in TWICE it often goes bad.