Viper’s Video Quicktags WordPress Plugin Discontinued

I’m officially discontinuing my Viper’s Video Quicktags WordPress plugin. It was one of the first plugins I ever wrote over 10 years ago. Back then embedding videos into WordPress posts was a chore and so I wrote the plugin to make the life of authors much easier.

Since then a lot has changed, namely the inclusion of native support in WordPress for even easier embeds, a feature that I actually contributed myself to WordPress.

Unfortunately users of my Video Quicktags plugin have been forced to keep the plugin activated so that embeds in old posts continue to work. Without the plugin, the shortcodes that the plugin created would cease working. So recently I wrote and released a tiny replacement plugin that creates those same shortcodes but has the native WordPress embed functionality handle the actual embedding of content.

If you are a Viper’s Video Quicktags plugin user, then I strongly recommend that you install my new plugin and then delete Viper’s Video Quicktags.

Besides switching away from a plugin I no longer support, advantages of the replacement plugin are modern, HTML5 embeds instead of Adobe Flash as well as automatic width to fit most themes, rather than fixed width independent of what theme you’re using.

It should be noted that the new plugin does not include the YouTube, Vimeo, etc. buttons in the editor but those are redundant due to how easy it is to embed videos directly from WordPress now — just paste the video’s URL on its own line.

Feel free to leave any questions or comments below.

66 thoughts on “Viper’s Video Quicktags WordPress Plugin Discontinued

        • Thanks! I made a copy of that post on my test site and the video embedded perfectly. I notice that your HTML is different from mine. It’s wrapped in a span that has the class video-container and the iframe has a title attribute too. You must have another plugin, or maybe some code in your theme, that is modifying embeds and doing a poor job at it, breaking the embed in the process. I’d temporarily disable all other plugins to see if that fixes it, and if so activate them one by one to see when it stops working again.

          • Hi Alex,
            I have been unable to successfully show the posts so far, despite the fact that i deactivated the plugins. While i was at it, my server started crashing 3 days ago after i installed Migrator plugin. Turns out, there are almost a million new entries in Postmeta table in SQL database.
            The entries are like this _oembed_time_e946c1d52428fd140bc1f153e2360f99
            and this _oembed_9fd773c93eb4e8998c63d8737b1f0e05
            There are almost a million entries like this causing my postmeta table to swell to 1.3 million entries. Whenever the database runs a query on the postmeta table, the server crashes.
            What do i do now? Can you tell me how do i get rid of these oembed entries and still keep my embedded videos intact?

            • Those entries are from WordPress itself. It’s the caches for the remote server requests that are used to get the embed HTML.

              Even without my plugin, entries like that would exist if you were to post a YouTube URL on its own line within a post. See https://codex.wordpress.org/Embeds

              Basically what happens is WordPress talks to YouTube and asks it for the embed HTML. This isn’t slow but it’s also not instantaneous so the answer is cached to the postmeta for the post that the embed lives in.

              However you should only have one entry per embed. If I had to guess (technical talk follows!), I’d say your theme is polluting the $post global variable and caching to the wrong post. This would mean you would have the cache for a single embed duplicated across multiple posts. This can happen if your theme is using the query_posts() function wrongly for example (most uses of that function are wrong). Another cause could be if you’re rendering posts say in a sidebar or something but not quite doing it right.

              Look to see if you have duplicates, for example if _oembed_time_e946c1d52428fd140bc1f153e2360f99 exists in multiple rows. Unless you have the same video embedded into multiple posts, this shouldn’t happen.

  1. Hi Alex. I had quicktime movies embedded in my wordpress template through your old plugin. They no longer work, despite using your new Migrator plugin. I still get the same error message “Video cannot be played because the file is corrupt”. I’ve tried reloading them and still get the same message. And ideas how to fix this?

  2. Previously QuickTime embeds were handled by a complicated bit of JavaScript and it required that QuickTime be installed. I don’t think it worked on a majority of Windows computers for example. That’s just the nature of trying to embed QuickTime.

    For my migrator plugin, I switched to letting WordPress handle it because it natively supports .mov files via the browser itself (no QuickTime needed). However apparently browser support isn’t perfect because I’m getting the same error in Firefox even when I directly visit a QuickTime video URL.

    Honestly, and this is going to be a pain, I would recommend sticking all of those QuickTime videos on YouTube, Vimeo, or some other type of video service, or alternatively converting them to H264/MP4 files (which most browsers can play without any plugins).

    QuickTime has been on its way out for ages and never worked well embedding in webpages, even back when QuickTime was popular. Even my old plugin wasn’t perfect as it because as I said I believe that it required that people have QuickTime installed (which most non-Mac users don’t).

      • No problem. I got to thinking though — I could probably wrap the QuickTime code from my old plugin into a separate tiny plugin of its own if you wanted. QuickTime still sucks and I recommend not using it going forward, but if converting over past posts isn’t practical, then this might be a decent compromise.

  3. Pingback: Best Rowing Machines | Health Greed

Leave a Reply