ryan

Module: Video embed for YouTube/Vimeo (TextformatterVideoEmbed)

Recommended Posts

Video embed for YouTube and Vimeo

ProcessWire Textformatter module that enables translation of YouTube or Vimeo URLs to full embed codes, resulting in a viewable video in textarea fields you apply it to.

How to install

  • Copy the TextformatterVideoEmbed.module file to your /site/modules/ directory (or place it in /site/modules/TextformatterVideoEmbed/).
  • Click check for new modules in ProcessWire Admin Modules screen. Click install for the module labeled: "Video embed for YouTube/Vimeo".

How to use

  • Edit your body field in Setup > Fields (or whatever field(s) you will be placing videos in). On the details tab, find the Text Formatters field and select "Video embed for YouTube/Vimeo". Save.
  • Edit a page using the field you edited and paste in YouTube and/or Vimeo video URLs each on their own paragraph.

Example

How it might look in your editor (like TinyMCE):

Here are two videos about ProcessWire

https://www.youtube.com/watch?v=Wl4XiYadV_k

https://www.youtube.com/watch?v=XKnG7sikE-U

And here is a great video I watched earlier this week:

http://vimeo.com/18280328

How it works

This module uses YouTube and Vimeo oEmbed services to generate the embed codes populated in your content. After these services are queried the first time, the embed code is cached so that it doesn't need to be pulled again.

The advantage of using the oEmbed services is that you get a video formatted at the proper width, height and proportion. You can also set a max width and max height (in the module config) and expect a proportional video.

Configuration/Customization

You may want to update the max width and max height settings on the module's configuration screen. You should make these consistent with what is supported by your site design.

If you change these max width / max height settings you may also want to check the box to clear cache, so that YouTube/Vimeo oembed services will generate new embed codes for you.

Using with Markdown, Textile or other LML

I mostly assume you are using this with TinyMCE. But there's no reason why you can't also use this with something like Markdown or Textile. This text formatter is looking for a YouTube or Vimeo video URL surrounded by paragraph tags. As a result, if you are using Markdown or Textile (or something else like it) you want that text formatter to run before this one. That ensures that the expected paragraph tags will be present when TextformatterVideoEmbed runs. You can control the order that text formatters are run in by drag/drop sorting in the field editor.

Thanks to Pete for tuning me into these oEmbed services provided by YouTube and Vimeo a long time ago in another thread.

  • Like 12

Share this post


Link to post
Share on other sites

No probs, but not sure it was me that mentioned oembed ryan - think I said I'd build this module and then never did (there's a theme there ;)).

Share this post


Link to post
Share on other sites

The good thing about oembed is that you don't rely on third party scripts/services and many services already support it - see Ryan's module code and you'll see YouTube and Vimeo's oembed URLs

As such, this module can easily be expanded upon to provide more services.

Share this post


Link to post
Share on other sites

Michael, that looks interesting. Looks like a lot of cool possibilities there and I look forward to taking a closer look and seeing if there might be another module brewing in there. But I have to admit that I find the whole oEmbed thing a bit vulnerable, as it's letting another web site populate raw markup into your site. You must have a lot of trust in whoever you let do that. It's more sensitive than linking to another service's JS. I have that level of trust with YouTube and Vimeo. I suppose I need to convince myself that something like embed.ly doesn't seem like a potential security timebomb, because the potential is very cool. I'm going to spend some more time looking at it.

  • Like 2

Share this post


Link to post
Share on other sites

This is great Ryan, thank you! My only comment is that Vimeo seems to default to https - for me at least. When I tried entering a url like

the formatter didn't seem to catch it. To my surprise I could see how to fix it by duplicating the vimeo section and adding changing it to https. Scary!
  • Like 1

Share this post


Link to post
Share on other sites

Thanks Marty, I was wondering about https URLs, but hadn't yet seen any so figured they didn't use them. I have just updated the module to support them, so they should work now (vimeo or youtube).

Share this post


Link to post
Share on other sites

Most of the time my customers want self hosted videos. Usually I give them a simple File-Field and embed the video with a <video> tag and include a javascript (mediaelementjs.com) with flash fallback for browsers without html5-video support.

Medialement.js even has a youtube plugin so you can Embed youtube videos like this:

<video width="640" height="360" id="player1" preload="none">
<source type="video/youtube" src="https://www.youtube.com/watch?v=nOEw9iiopwI" />
</video>

I have not used this module yet, but maybe Medialement.js is a interesting option to include?

Share this post


Link to post
Share on other sites

Mediaelement looks pretty cool, I actually have a use for this on another project and am glad to find out about it. I need to take a closer look to determine if this is something that fits the URL-to-embed code purpose of the module without stepping over the line on front-end dev. But it certainly fits with the name and purpose of the module.

Modal popups are a good idea, but things that might be better in one's front-end development rather than in a text formatting module, given that they are more site/need specific and involve linking to local javascript files and such. These common YouTube/Vimeo video embeds are pretty much universal to the point where one almost expects one of their URLs to convert to a player, so that's what the purpose is here. And that's the most likely way this module would grow (adding more services). Still, this module may be a good starting point for branching in less universal, more site specific needs, and I'd encourage extending it like that.

Share this post


Link to post
Share on other sites

OT: Re: Embed.ly - They totally lost my trust with that reversed gradient on hover in navigation. Doh.

---

Also, Ryan, are you on fire or have you just finished million client projects? You seem to work 50 hours a day, lately.

Share this post


Link to post
Share on other sites

He perfected his clone() function in PW and it now clones humans too ;)

Share this post


Link to post
Share on other sites
Also, Ryan, are you on fire or have you just finished million client projects? You seem to work 50 hours a day, lately.

I wish that was me. You are thinking of Marty. :) I've not launched a bunch of projects lately, not by a long shot. The ones I posted about in Pub a month or two ago were done over a long period of time.

Share this post


Link to post
Share on other sites

Oh Marty's on fire alright, but it seems that new things in PW are coming faster than usually lately, so I thought you have somewhat less client work or so.

  • Like 2

Share this post


Link to post
Share on other sites

I saw that but didn't comment :D I've no idea why the software allows you to like yourself but it does...

Share this post


Link to post
Share on other sites

I thought that was edit button, I'm mobile today. O tapped random thibgs to edit :D Somehow I made the reply text smaller as well.

Share this post


Link to post
Share on other sites
I thought that was edit button, I'm mobile today.

Yeah yeah, we believe you ;)

Share this post


Link to post
Share on other sites

Hi all,

I'm trying to use the Embed video module, but it doesn't work for me... I followed the documentation, but it failed and I keep wondering what I am doing wrong.

Here's my work :

  • Module upload in 'site/modules/' > Check new module > installation
  • Setup > Fields > body > Details > Textformatters > Video embed
  • In my page body field, I have 2 Youtube links, but they stay as links (no embed...).

If you want to have a look at the page, here it is : http://flenglish.tux...s/the-alphabet/

Thanks for your concern ;-) (And sorry not to be able to find the answer myself...)

Share this post


Link to post
Share on other sites

@celfred, you've got two problems in that example:

  • YouTube links need to be alone in their own paragraphs, there shouldn't be any other content in same <p> tag -- try adding the descriptions below or above actual YT links (also: now they're in a list, which probably won't work either)
  • Don't make them actual hyperlinks; I might remember wrong, but IMHO that way they won't work -- just plain URL as a string without the <a> tag

I hope this helps a bit.

  • Like 2

Share this post


Link to post
Share on other sites

@teppo, Thank you for your help ! It works better now although I had tried doing this, but on the second link and it never worked. Actually, this second link still doesn't work. I've changed it with another equivalent video (for my purpose), and the new link works...

I can't tell what the problem is... If I copy and paste this link, the video is available...

If someone is interested in understanding the issue, here are my 3 Youtube links (preceded by https://www.youtube.com/ [to avoid the max number of media error I get posting in the Forum]):

  1. watch?v=8-NeizIkHBY
  2. watch?v=Imum21-hdNg
  3. watch?v=dsO__o4Ezjw

Number 1 and number 3 : Video embed without any problem since I followed teppo's advice (in their own paragraph's tags).

Number 2 : no embed... Just a regular text...

Thanks again !

Again, if you want to see the original article : http://flenglish.tux...s/the-alphabet/

Share this post


Link to post
Share on other sites

@celfred, either the video you're trying to embed has embedding disabled or this could be a problem (or feature, can't really tell yet) at YouTube. There's similar problem reported at the WordPress bug tracking system here: http://core.trac.wordpress.org/ticket/14377.

This example you gave returns code 401 Unauthorized and this is what oembed.com has to say about this particular error code:

The specified URL contains a private (non-public) resource. The consumer should provide a link directly to the resource instead of any embedding any extra information, and rely on the provider to provide access control.

Will have to do some more testing later.. unless, of course, someone else knows a solution / answer to this problem already :)

  • Like 2

Share this post


Link to post
Share on other sites

I am having problems with this module. It seems to save the embed codes into the database, which is good. Bad thing is that it saves only one line there. This causes every video to be the same. It seems to fail on video_id part, since my only row in textformatter_video_embed table is this:

www.
<iframe width="640" height="360" src="https://www.youtube.com/embed/9StIWIg03eM?fs=1&feature=oembed" frameborder="0" allowfullscreen></iframe>
2012-09-19 10:40:44

So it saves only www. as video_id and seems to that with every video. Is this problem only on my installation or are other experiencing the same? My url in textarea is in this format:

https://www.youtube.com/watch?v=9StIWIg03eM&feature=related
  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By FrancisChung
      Hi,
      I was wondering if anyone knew what this did? 

      If so, do you know what modules it actually impacts? Is there another log that lists the action it took?

      I'm having some weird problems with PHP duplicate declaration per link below, since this module was run.
       
       
    • By tpr
      AdminOnSteroids
      Various admin tweaks to enhance ProcessWire admin.
      http://modules.processwire.com/modules/admin-on-steroids/
      https://github.com/rolandtoth/AdminOnSteroids

    • By Macrura
      Field Descriptions Extended
      This module enables you to extend field descriptions by dividing short descriptions with a longer text that is revealed in a toggle.
      Github: https://github.com/outflux3/FieldDescriptionsExtended
      Extending your field descriptions using the standard field's description field.
      Once this module is installed, it will automatically search your description field for the presence of 5 dashes (-----).
      Any content above the 5 dashes will be visible and the content below the dashes will be hidden. A 'More...' link will appear at the end of the short description which when clicked will reveal the rest of the description.
      Using Simple Markdown Editor with the description field
      If you have Simple Markdown Editor (InputfieldSimpleMDE) installed, you can enable the field description to have that editor.
      *When using Simple MDE, you can use the button (Insert Horizontal Line) instead of typing 5 dashes. More about SimpleMDE.
      Extending your field descriptions using content from a ProcessWire Page for the field description.
      You may use the content from a ProcessWire page as a field description. This would allow you to easily insert images, links, and use hanna codes.
      To use page content for your field descriptions, please follow these instructions:
      Install Select Fields module (FieldtypeFields) http://modules.processwire.com/modules/fieldtype-fields/ Create a new field using this field type, e.g. field_select. Add the field to any template you will be using for your field descriptions. Setup your help pages (for example under a settings branch) where you will store the field description content,using the template containing the Field Select. Add content to a page and select the field where that content should show. To show a short text before the link to the longer content, separate them with 5 dashes Be sure to update your settings on this page, first enable page content descriptions,then specify the name of the Select Fields field, template to search, and content field. If you create a field description using this method, please note that the description field must be blank for contexts where you want the page content to appear.
      You can freely use template context for field descriptions, but the Page Content method is not context sensitive and will display under all contexts where the description is blank.
      ----
      original post:
      This is a new module, hope to release soon, which allows extended field descriptions, in currently 2 ways.
      The main feature of the module is that you can have a short description and then a 'more...' link which drops down a longer block of text.
      This is achieved by separating the intro/visible text and the rest with 5 dashes.

      Example setup:

      the 2nd way is if you are using AdminThemeUiKit, you can show extended field instructions in a panel. The content of the panel is edited on a regular PW page. This use case would probably not be that common, but if you had a field that required some extended instructions for how to use, this could be useful; Also, since this allows you to target information and instructions down at the field level, it could reduce the amount of documentation needed on a global level, since it is a lot more context targeted.

    • By netcarver
      Part 1 of a 2 part Module & Service Reveal.
      I'm currently working on a new module: ModuleReleaseNotes that was inspired by the work I originally did on making Ryan's ProcessWireUpgrades module "release" aware. In the end, I decided to ditch the approach I was originally taking and instead work on a module that hooked in to the UpgradeConfirmation dialog and the module edit page.
      Aims
      My aims for this module are as follows...
      Make discovery of a module's changes prior to an upgrade a trivial task. Make breaking changes very obvious. Make reading of a module's support documentation post-install a trivial task. Make module authors start to think about how they can improve the change discovery process for their modules. Make sure the display of information from the module support files/commit messages doesn't introduce a vulnerability. Looking at these in turn...
      Making discovery of a module's changes prior to upgrade a trivial task.
      This is done by adding a "What's changed section" to the upgrade confirmation dialog.  This section takes a best-effort approach to showing what's changed between the installed version and the updated version that's available via the module repository.
      At present, it is only able to talk to github-hosted repositories in order to ask them for the release notes, the changelog file (if present) and a list of commits between the git tag that matches the installed version and the tag matching the latest version.
      It will display the Release Notes (if the author is using the feature), else it will display the commits between the tags (if tagging is used by the module author) else it will show the changelog file (if present) else it will show the latest N commits on the master branch (N, of course, being configurable to your liking.)
      An example of the Github Release Notes pulled in for you, taken from Mike Rockett's TextformatterTypographer Module...

      An example of a tag-to-tag commit list from the same module...

      An example of a changelog - formatted to show just the changes (formatting styles will change)...

      Finally, an example of a fallback list of commits - sorry Adrian ...

       
      Making breaking changes obvious.
      This is currently done by searching for a set of configurable search strings. Later versions may be able to support breaking change detection via use of Semantic Versioning - but this may require some way of signalling the use of this versioning standard on a module-by-module basis.
      For now, then, you can customise the default set of change markers. Here I have added my own alias to the list of breaking change markers and the changes section of the changelog is styled accordingly (these will be improved)...

       
      Make reading of a module's support documentation, post-install, a trivial task.
      This is done by making some of the support files (like the README, CHANGELOG and LICENSE files) readable from the module's information/settings screen. There is an option to control the initial open/closed state of this section...

      Here is Tracy's README file from within the module settings page... 

       
      Make module authors start to think about how they can improve the change discovery process for their modules.
      There are notes in each of the sections displayed on the upgrade confirmation page that help authors use each of the features...

       
      Make sure display of external information doesn't introduce a vulnerability.
      This is an ongoing concern, and is the thing that is most likely to delay or prevent this module's release lead to this module's withdrawl should a vulnerability be found. Currently, output is formatted either via Markdown + HTML Purifier (if it was originally a Markdown file) or via htmlspecialchars() if it has come from a plaintext file.
      If you discover a vulnerability, please get in contact with me via the forum PM system.
       
      Ongoing...
      For now, I've concentrated on integration with GitHub, as most people use that platform to host their code. I know a few people are hosting their repositories with BitBucket (PWFoo comes to mind) and some with GitLab (Mike Rockett?) and I would eventually like to have adaptor implementations for these providers (and perhaps GitKraken) - but for now, GitHub rules and the other hosts are unsupported.
       
      Links
      Github: ModuleReleaseNotes
      PW Module Repository: Here (pending?)