I’m finally getting around to testing the best way to embed a video in blog post. It’s possible that different browsers will produce different results. My tests below were performed in a Chrome browser.
Method #1:
Click Insert > Media > Paste YT link in Source Box > Click OK
Result: Preview of video immediately appears in blog post edit box.
Method #2:
At YouTube.com, under chosen video, click Share > Embed > Copy code
At BillWhittle.com in blog post box click Insert > Media > Embed Tab > Paste code > Click OK
Result: Preview of video immediately appears in blog post edit box.
Method #3:
Paste URL link in the blog post box on a line by itself.
Result: Not known until after posting.
CONCLUSION:
The most illogical, and simplest, method (#3) is the one that worked. Your mileage may vary. Back to the drawing board.
6 replies on “Testing Video Embed in Blog Post”
The move to the new server un-embedded all of my previous posts where I used Scott’s Method #2. All of them.
I tried Scott’s Method #3, and that does not work for me, either, after the server move.
Method #2 worked for quite awhile, but since the move to the new server, it does not work.
When I have more time, I will try to problem solve this.
Thank you all for your input.
Unfortunately, because this transmogrification occurs after the edited content is submitted, I can’t diddle with that code to do kewl things like putting it to one side and flowing text around it, or putting it up in a very annoying floating window like Foxnews does. Dang. I am an inveterate diddler.
Not illogical, Scott, it’s the way we’ve always done it before (minus the span around it to given the object centerability etc)! Have you compared this to what the final code looks like? It’s on line 626 of the code my browser sees. All it’s done is surround it with an iframe and add some attributes:
<iframe width=”615″ height=”346″ src=”https://www.youtube.com/embed/KvAk9718Jo8?feature=oembed” frameborder=”0″ allow=”accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture” allowfullscreen></iframe>
Aha! The editor added the /embed/ and the feature=”oembed” to the src URL! Perhaps it queries YT to get a different src line before creating the interpretation (or perhaps it assumes it).
The iframe comes with the YT embed code.
But my point was that the plain URL is converted into the embed code by the editor, automatically. You don’t have to copy it using the Share->Embed->Copy code option.
Since the embed code is the same, logic implies that it might be possible the editor is adding something else, beyond just the iframe, that’s enabling it? A class or bit of javascript? I’m not fluent enough in modern web languages to be able to dig through the 2000+ lines of code to understand it well.
Yup–method 3 seems to be the only functional one at the moment. Convenient that it’s also the easiest!