Jump to content
ryan

Module: Video embed for YouTube/Vimeo (TextformatterVideoEmbed)

Recommended Posts

Same here with chrome, I think it is tinymce that is adding the link.

Share this post


Link to post
Share on other sites

Hi! Is it possible to return the videoID from the module's output? Would come in handy when trying to generate Youtube/Vimeo thumbnails for my template.

Share this post


Link to post
Share on other sites

Not sure that I understand where it would return to. Can you provide more detail? Textformatter modules happen behind the scenes and manipulate the text directly, rather than returning anything. That's why I'm not sure I understand the question.

---Edit:

Thinking more, it does have the video ID at one point in the module, so you could modify the module to make it insert thumbnails as part of the text formatting it does. This is probably the way I would approach it at least.

Share this post


Link to post
Share on other sites

Just a note if you are wanting YouTube to be responsive (which it is not out of the can)

Then I stole this from http://avexdesigns.com/responsive-youtube-embed/

Add this css somewhere:

.video-container {
    position: relative;
    padding-bottom: 56.25%;
    padding-top: 30px; height: 0; overflow: hidden;
}

.video-container iframe,
.video-container object,
.video-container embed {
    position: absolute;
    top: 0;
    left: 0;
    width: 100%;
    height: 100%;
}
 
The do this to your poor body block:
 
<div class="video-container"><?php echo $page->body; ?></div>

Obviously this probably only works neatly with just ONE video!

Hmmm ... perhaps an alternative module-field type that is just a text box might be a good idea for this.

  • Like 1

Share this post


Link to post
Share on other sites

@Joss, so far I know that css code is injected inline in the output of the embed tag if you checked the responsive option in the TextformatterVideoEmbed settings.

  • Like 2

Share this post


Link to post
Share on other sites

There is one?

Oh, I will go look

Interesting set of errors in chrome, by the way, which seems to object to the iframe:

Unsafe JavaScript attempt to access frame with URL

I gather this is a common Chrome problem, however.



Oh yeah!!! :)

Okay, scrub my previous post.

Share this post


Link to post
Share on other sites

About the errors, thats normal. Google allows all kind of advertisement scripts and other bandwidth eating scripts to access the iframe.

Share this post


Link to post
Share on other sites
About the errors, thats normal. Google allows all kind of advertisement scripts and other bandwidth eating scripts to access the iframe.

A nuisance with me though - I always have to wade through the list of errors I create myself; I don't need chrome adding to my woes. :)

  • Like 1

Share this post


Link to post
Share on other sites

Is there any way of making this work outside of a tinyMCE or equivalent field, ideally a plain text field or if not a standard textarea field?

I gather this is meant more for on the fly inclusion of videos within textareas but I'm looking for something specifically for a video template.

In the past I've got them to find the embed code and I've factored that into my templates but the url would be easier! :)

Share this post


Link to post
Share on other sites

Just in case this is of help, I use this code from Ryan to turn a YT URL in it's own paragraph into an embedded  YT vid.

Thanks Alan, will take a look but I think this approach is what has now been turned into this module. I think what I'm almost after is a youtube or vimeo fieldtype so I don't have to present the client with a tinyMCE field to put his url in.

  • Like 1

Share this post


Link to post
Share on other sites

Welcome, only sorry it's no help :/

  • Like 1

Share this post


Link to post
Share on other sites

There's a ton of controls you can call on depending on the code you use to embed. It's ages since I looked but I Googled and dev pages on youtube.com had lots of advice, so I am guessing that, especially with the rise of HTML5 will be the place to go to get the appropriate embed to establish HTML5 over Flash as a pref'.

Share this post


Link to post
Share on other sites

Thanks Alan, I'm using the module at the moment so not sure if there is a preference in there that affects it.

Share this post


Link to post
Share on other sites

You can use the module in a text field also, but because it will look for <p> tags around the video, make sure you also choose textile or markdown before the video formatter on that same field. It works, but it's a lot of unnecessary processing for something that simple.

Or you could do this without a module. Just create a video ID field, and embed the video like this

echo "<iframe width='560' height='315' src='http://www.youtube.com/embed/{$page->videoID_field}'></iframe>";

If you want to control some aspects of the player add as many of these parameters as you wish to the video url https://developers.google.com/youtube/player_parameters

echo "<iframe width='560' height='315' src='http://www.youtube.com/embed/{$page->video_id}?autoplay=1&theme=light'></iframe>";

And if you want, those parameters can be dynamic:

echo "<iframe width='560' height='315' src='http://www.youtube.com/embed/{$page->video_id}?autoplay={$page->video_autoplay}&theme={$page->video_theme}'></iframe>";
  • Like 1

Share this post


Link to post
Share on other sites

Thanks Diogo.

The end user would just find the video id and paste that in? That's sort of what I was doing with the embed codes, just thought the url would be easier for them but if it's just the number bit, probably OK.

Thanks for the tip about the text fields, I may try the module on that!

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.

Dear Ryan, like user interrobang, I also have self hosted videos on my Linux server and I'm interested to try your module.

All my self hosted videos have the same URL structure: http://my.internal.server/streaming/videos/name-of-the-video

(where "name-of-the-video" changes every time). Hoy could I tweak your "TextformatterVideoEmbed.module" in order to use it with this type of URL?

I'm not a php coder, so I'm quite scary about tweaking your code.

Regards!

Share this post


Link to post
Share on other sites

I'm not really sure how this module could be tweaked for local videos, as it's built around oembed, so really more about web services than local hosting. I think that the best solution for local video hosting will depend largely on what player you want to use to display the videos.

Share this post


Link to post
Share on other sites

Yes Ryan, you're right. I'm using the phpmotion.com platform (a youtube-clone) on a local linux server, to upload videos and convert them.

Like youtube, also phpmotion provide both the link and the embedding html structrure.

Currently I'm simply using the HTML embed into a textearea field, but I was wondering if there's any way to pass the link and automatically build the embedding structure.

An example:

generated internal link: 

http://myserver/videos/title
 

and its standard embedding structure (tweakable):

<embed src="http://myserver/player.swf" width="320" height="256" bgcolor="FFFFFF" allowscriptaccess="always" allowfullscreen="false" flashvars="flvsource=http://myserver/uploads/PZDBCClXAP0td1rgBPqE.flv&preview_image=http://myserver/uploads/player_thumbs/PZDBCClXAP0td1rgBPqE.jpg&backgcolor=FFFFFF&autoplay=true&url_logo=http://myserver/images/playerlogos/logo-player.png&logo=top_right&floating_navbar=false&color_nav_bar_top=0x478dc2&color_nav_bar_bottom=0xE7EBEC&ads_background_color=0x00CCFF&ads_border_color=0xCCCCCC&scrubber_position_color=0x6AA1CE&scrubber_load_color=0x888888&scrubber_background_color=0xBBBBBB&volume_bar_color=0xBBBBBB&aspect_ratio=stretch"></embed>
 

Probably it's not possible, because of the source (random_name.flv).

Thank you! Regards.

Share this post


Link to post
Share on other sites

What do you mean the source is random? On the embed code above, you are refering to this "PZDBCClXAP0td1rgBPqE.flv"?

Share this post


Link to post
Share on other sites

What do you mean the source is random? On the embed code above, you are refering to this "PZDBCClXAP0td1rgBPqE.flv"?

Yes, the embedding code is generated by phpmotion. It's really a good platform, but probably there's no way to make the embedding automatic.

Share this post


Link to post
Share on other sites

But that's the name of the vídeo on the url, right? You have access to that code from the url to put it on a field in the admin, I guess.

If so, It would be enough to have a normal text field where you put that code without the extension, and have the embedding code on the template:

echo '<embed src="http://myserver/player.swf" width="320" height="256" bgcolor="FFFFFF" allowscriptaccess="always" allowfullscreen="false" flashvars="flvsource=http://myserver/uploads/' . $page->video_code . 'flv&preview_image=http://myserver/uploads/player_thumbs/' . $page->video_code . '.jpg&backgcolor=FFFFFF&autoplay=true&url_logo=http://myserver/images/playerlogos/logo-player.png&logo=top_right&floating_navbar=false&color_nav_bar_top=0x478dc2&color_nav_bar_bottom=0xE7EBEC&ads_background_color=0x00CCFF&ads_border_color=0xCCCCCC&scrubber_position_color=0x6AA1CE&scrubber_load_color=0x888888&scrubber_background_color=0xBBBBBB&volume_bar_color=0xBBBBBB&aspect_ratio=stretch"></embed>";
 

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...