Jump to content
Lex Sanchez

Module: Video or Social Post Embed

Recommended Posts

Video or Social Post Embed

Based on the TextformatterVideoEmbed module developed by Ryan Cramer, we have added the possibility to embed publications of the main social networks Facebook, Twitter and Instagram.

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

How to install

  • Download or Clone from Github: https://github.com/lexsanchez/VideoOrSocialPostEmbed

  • Copy the VideoOrSocialPostEmbed.module file to your /site/modules/ directory (or place it in /site/modules/VideoOrSocialPostEmbed/).

  • Click check for new modules in ProcessWire Admin Modules screen. Click install for the module labeled: "Video or Social Post Embed".

  • Now you will be on the module config screen. Please make note of the config options and set as you see fit.

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 or Social Post Embed". Save.

  • Edit a page using the field you edited and paste in YouTube, Vimeo, Facebook, Twitter, Instagram and/or Issuu URLs each on their own paragraph.

Example

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

Here are two videos about ProcessWire

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

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

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

http://vimeo.com/18280328

Embed social post and Issuu Presentation:

https://www.instagram.com/p/BeA8p9AhA3b/

https://twitter.com/rpc_radio/status/954315569838411776

https://www.facebook.com/TNTLA/videos/10155549598252758/

https://issuu.com/madsoundsmagazine/docs/mad_sounds_issue_no._17_issuu

How it works

This module uses YouTube, Vimeo, Instagram, Facebook, Twitter and Issuu 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.

Configuration

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/Facebook/Twitter/Instagram/Issuu oembed services will generate new embed codes for you.

Using with Markdown, Textile or other LML

This text formatter is looking for a YouTube, Vimeo, Instagram, Facebook, Twitter or Issuu 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 VideoOrSocialPostEmbed runs. You can control the order that text formatters are run in by drag/drop sorting in the field editor.


Copyright 2018 by Ryan Cramer / Updated by Lex Sanchez

  • Like 18

Share this post


Link to post
Share on other sites

Thank you.

There is a problem here with 

https://www.instagram.com/p/BeA8p9AhA3b/

 

Error: Exception: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'embed_code' at row 1 (in /home/theo/public_html/pwdev/site/modules/VideoOrSocialPostEmbed/TextformatterVideoOrSocialPostEmbed.module line 113)

#0 /home/theo/public_html/pwdev/site/modules/VideoOrSocialPostEmbed/TextformatterVideoOrSocialPostEmbed.module(113): PDOStatement->execute()
#1 /home/theo/public_html/pwdev/site/modules/VideoOrSocialPostEmbed/TextformatterVideoOrSocialPostEmbed.module(337): TextformatterVideoOrSocialPostEmbed->getEmbedCode('://api.instagra...', 'ig-BeA8p9AhA3b')
#2 /home/theo/public_html/pwdev/site/modules/VideoOrSocialPostEmbed/TextformatterVideoOrSocialPostEmbed.module(152): TextformatterVideoOrSocialPostEmbed->embedInstagram('<p>https://www....')
#3 /home/theo/public_html/pwdev/wire/core/Textformatter.php(60): TextformatterVideoOrSocialPostEmbed->format('<p>https://www....


 

Share this post


Link to post
Share on other sites

Hello Theo:

Thanks for your comment; I have made an update to the module that solves this error, please uninstall the module replace with the new version.

Regards,

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, would be interesting to see how your example looks like on the frontend. Maybe you have a screenshot? :)

  • Like 2

Share this post


Link to post
Share on other sites

Is there a way to get this module to work with CKeditor? For me it is not working :( Only the links are visible in frontend.

Share this post


Link to post
Share on other sites

Hello,

When I try to install Video or Social Post Embed in ProcessWire 3.0.102, I have an error page with:

Error

Class '\VideoOrSocialPostEmbed' not found

and

File: /home/********/public_html/wire/core/Modules.php:535

525:                    ProcessWire::setCurrentInstance($wire2);
526:                } else {
527:                    $wire1 = null;
528:                }
529:            } else {
530:                $wire1 = null;
531:                $wire2 = null;
532:            }
533:            
534:            try {
535:                $module = $this->wire(new $className());
536:            } catch(\Exception $e) {
537:                $this->error(sprintf($this->_('Failed to construct module: %s'), $className) . " - " . $e->getMessage());
538:                $module = null;
539:            }

In version 2.8.62, the class wasn't found as well.

If I disable Tracy Debugger, I see:

Fatal error: Uncaught Error: Class '\VideoOrSocialPostEmbed' not found in /home/********/public_html/wire/core/Modules.php:535 Stack trace: #0 /home/********/public_html/wire/core/Modules.php(1704): ProcessWire\Modules->newModule('\\VideoOrSocialP...') #1 /home/********/public_html/wire/core/Wire.php(386): ProcessWire\Modules->___install('VideoOrSocialPo...', Array) #2 /home/********/public_html/wire/core/WireHooks.php(723): ProcessWire\Wire->_callMethod('___install', Array) #3 /home/********/public_html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Modules), 'install', Array) #4 /home/********/public_html/wire/modules/Process/ProcessModule/ProcessModule.module(262): ProcessWire\Wire->__call('install', Array) #5 /home/********/public_html/wire/core/Wire.php(380): ProcessWire\ProcessModule->___execute() #6 /home/********/public_html/wire/core/WireHooks.php(723): ProcessWire\Wire->_callMethod('___execute', Array) #7 /home/********/public_html/wire/core/Wire.php(442): ProcessWire\WireHooks->runH in /home/********/public_html/wire/core/Modules.php on line 535

and

Error: Uncaught Error: Class '\VideoOrSocialPostEmbed' not found in /home/********/public_html/wire/core/Modules.php:535
Stack trace:
#0 /home/********/public_html/wire/core/Modules.php(1704): ProcessWire\Modules->newModule('\\VideoOrSocialP...')
#1 /home/********/public_html/wire/core/Wire.php(386): ProcessWire\Modules->___install('VideoOrSocialPo...', Array)
#2 /home/********/public_html/wire/core/WireHooks.php(723): ProcessWire\Wire->_callMethod('___install', Array)
#3 /home/********/public_html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Modules), 'install', Array)
#4 /home/********/public_html/wire/modules/Process/ProcessModule/ProcessModule.module(262): ProcessWire\Wire->__call('install', Array)
#5 /home/********/public_html/wire/core/Wire.php(380): ProcessWire\ProcessModule->___execute()
#6 /home/********/public_html/wire/core/WireHooks.php(723): ProcessWire\Wire->_callMethod('___execute', Array)
#7 /home/********/public_html/wire/core/Wire.php(442): ProcessWire\WireHooks->runH (line 535 of /home/********/public_html/wire/core/Modules.php) 

This error message was shown because: site is in debug mode. ($config->debug = true; => /site/config.php). Error has been logged.

EDIT: I've just been able to install it via the backend (via the .zip URL from GitHub).
I had done it manually before. I had renamed the folder and the .module file VideoOrSocialPostEmbed (like in the documentation(s)). I hadn't done it again without renaming anything (or had I? I don't remember. Perhaps both, or the folder or the file) so I don't know if it was the reason (or one of them).
I've changed the PHP version from 7.1 to 7.2. Not sure it had an effect.

Edited by Christophe
Solved

Share this post


Link to post
Share on other sites

Hello again,

For YouTube videos, would it be possible to make it work with ?rel=0 added at the end of the URL, so that suggestions aren't displayed when pausing or when the video ends.

It works with the Video embed for YouTube and Vimeo module.

Thanks in advance for considering it.

Or if anyone knows how to enable it properly.

Share this post


Link to post
Share on other sites

Nice module.

You should add this:

 $embedCode = utf8_encode($data['html']);


When fetching data from providers, and set the data tables to mb4. Otherwise the output gets chewed up and throws errors. 

Test with instagram embed where there is an emoji in the title, e.g. https://www.instagram.com/p/BjXM8mInfN-/

Thanks for the module. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...