![]() (Again, this isn’t a problem for big players like YouTube and Vimeo, but it does happen to smaller sites.) What this means is that right now the code is legit, but if the hosting service goes out-of-business and someone else buys the domain, they can inject all sorts of malware, bitcoin mining code and other nastiness where that video player used to be. But if it’s a site the CMS doesn’t recognise, it will assume the code could be hijacked. ![]() That’s fine if the CMS knows the content is coming from YouTube. ![]() If you want to embed content from sites like YouTube, you need to paste in code that looks like this: That means unchecked code that deviates from simple things like paragraph tags, bulleted lists, bold text, links and so on. The problemĪs I mentioned, WordPress doesn’t want you posting “arbitrary HTML”. It’s not as pretty as Anchor’s player, but it gets the job done. Just paste in the URL to an episode hosted on Anchor, then copy the MP3 URL the tool gives you, paste that into an “Embed” block on, and WordPress will create an audio player block. Luckily we can get around that through a simple tool that will get the audio URL for an Anchor episode from its webpage. That’s because Anchor’s website isn’t configured correctly, and doesn’t allow you to paste arbitrary pieces of HTML code into its CMS for fear of that code getting hijacked (the latter is sane, the former is due to Anchor mostly being a toy, rather than a serious podcast hosting service). ![]() After doing some research for an upcoming course on turning a blog into a podcast, I discovered that, contrary to what I’d assumed, you can’t embed the Anchor audio player for an episode into a blog post hosted on. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |