Wiredrive Player

This plug-in allows you to embed Wiredrive video reels and image galleries into your WordPress-powered website.

Author:Wiredrive (profile at wordpress.org)
WordPress version required:3.4.0
WordPress version tested:4.9.15
Plugin version:3.1.1
Added to WordPress repository:07-02-2011
Last updated:26-06-2020
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Rating, %:0
Rated by:0
Plugin URI:http://wordpress.org/extend/plugins/wiredrive...
Total downloads:5 753
Active installs:20+
plugin download
Click to start download

Wiredrive WordPress Plug-in Features:

  • Customizable dimensions
  • Displays videos and/or images, title and a configurable number of credits of each asset
  • Multiple layout options
  • Show or hide thumbnail tray
  • Customizable color options
  • Works with AirPlay
  • Click through assets or play them as a slideshow
  • Leverage assets already uploaded Projects or Library
  • Download and install in a few clicks
  • Elegantly replaces YouTube, Vimeo and other media hosting sites

Functionality Specs:

  • Displays asset, title and first credit of each asset
  • The active asset’s thumbnail will have a border
  • Videos play through Flash in Firefox, Internet Explorer and Chrome. If Flash isn’t installed, the user is prompted to install Safari or Flash
  • In Safari/iOS, videos play natively using the HTML5 player
  • Assets will play sequentially
  • Displays the first asset’s poster frame if it’s a video (unless autoplay is enabled and supported)
  • Works with all valid Wiredrive presentation URLs (short link, mRSS, email, etc.)
  • If the feed does not come from Wiredrive an error is returned
  • If the feed is empty an error is returned
  • If the feed does not exist an error is returned

Backwards Compatability Notes:

  • Theme changes: As of version 3.0, Grid and Grid-box themes have been merged into one theme called the Gallery theme. When the player detects a post with shortcode from an older version of the player that used either grid or grid-box themes, it will translate them as best it can into a Gallery theme equivalent, hopefully meaning you won’t need to regenerate the shortcode for your post. The theme translation strategy is as follows:
    • “grid” theme becomes “gallery-player” with thumbnail strategy set to “scale” and the thumbnail dimensions set to 180×180
    • “grid-box” theme becomes “gallery-player” with the thumbnail strategy set to “scale”, the thumbnail dimensions set to 180×180, and center-align thumbnails (letterboxing) turned on
  • The structure of the markup has drastically changed. If you have custom stylesheets defined to override the default styles of the player (styles that are not covered by the Player’s admin color preferences), they will need to be updated to reflect the new markup.

Known issues:

  • iPad: Autoplay videos is not supported on the ipad. This is a limitation set by Apple with no workarounds. Because of this limitation, autoplay will only perform a function on iOS if the entire presentation consists of images and slideshow is enabled. If there is a video at any position in the presentation, it can not be guaranteed that the video will start playing when slideshow’ed into due to the additional limitation of only being able to programmatically play html5 video on iOS if the play command is in an execution stack that originates with a user interaction event (click, touch, etc) (Slideshows change the asset through a timeout, which is not a user interaction event)
  • iPad: No flick/swipe gesture support for the carousel. We’d like to keep the dependencies of this plugin as small as possible (jQuery and jQuery UI being the only dependencies) and support for this is not built into jQuery. We felt this feature alone wasn’t worth adding an additional dependency or the increased size of the player script by 33%.
  • iPad: Pagination arrows will not appear in the inline player on mobile devices due to an iPad bug that does not allow processing of events on elements that are positioned over a video element with native controls
  • IE8 does not support the Crop thumbnail strategy for galleries (although strangely enough, it works in IE8 emulation mode inside of IE9…). The crop strategy renders the thumbnail bounding box according to its specified dimensions and then sets the thumbnail of the asset as the background image of the bounding box (centered vertically and horizontally), making the bounding box act as a cropping mask for the thumbnail. IE8 does not handle background image scaling/positioning well, and the pillarbox/letterbox opacity -ms-filter directive conflicts with the background image. Because of this, IE8 will render all gallery thumbnails using the Scale strategy. All other supported browsers will respect the Crop strategy.
  • IE8: Shortcode will always be inserted at the beginning of the text editor, regardless of where the text cursor is. This is a bug inside TinyMCE.
  • Firefox: When the gallery modal player is opened, the main page behind the skrim may jump to the top of the page while the skrim is open and then when the skrim is closed jump back to the scroll position the page was in before the skrim opened. This is probably because there is a rule in the wordpress theme stylesheet (or perhaps another plugin) that defines an important margin-top css rule on the html element. Firefox automatically scrolls to the top of the page when overflow: hidden is applied to the html element. To counter this, the page is programmatically shifted to the correct position via an inline margin-top rule applied to the html element. An important rule will supersede this countermeasure, causing the bug to reappear.
  • A flash of miscaled, misaligned stale images may appear while transitioning between two images. This is probably because the user has local caching disabled. Image transitions happen by opacity fading between two absolutely positioned image elements (the current image and the next image). The player preloads all presentation images in memory to avoid this flickering, but if local caching is disabled, it will have to fetch the next image every time causing a delay in the correct image appearing that the fader cannot anticipate.

FAQ
ChangeLog