WordPress.org

Ready to get started?Download WordPress

Plugin Directory

SWFPut - SWFlash Put

SWFPut provides a video players for posts and pages and widget areas, as both flash and HTML5 video.

2.1.1

  • This release is called "Sigh" and its only change is a workaround for a chromium 3.4 bug -- not on the front end, but in the Visual editor plugin. You want details, you say? OK: this plugin's video in the tinymce visual editor is housed in an iframe element. The iframe was given, for principle only, a sandbox attribute (with the "allow-scripts" argument), even thought the content is generated by a plugin script and is a known quantity. This worked in the major browsers including the Chromium 22 and 3.[123] tested with, but Chromium 3.4 would no longer run scripts in the iframe. Persons-of-curiosity may web search 'chromium iframe scripts' and see at a glance that Chromium has dithered on this subject. Bottom line: the sandbox attribute is removed. Apologies for this release so soon after 2.1 a few days ago.

2.1

  • Several small bug fixes and improvements.
  • Now, by default HTML5 video will be placed as primary content with flash as fallback (see settings page).
  • Now, if the stop button is clicked the initial poster image, if provided, should reappear.
  • Better handling of unsupported HTML5 video types: if an MP4 was given it will passed to the flash player when necessary.

2.0

  • Video will now display in the TinyMCE "Visual" editor. This requires HTML5 compatible video files, and a recent and not-too-buggy browser (Chromium is fine on GNU/Linux, but as on MS it might not run the script in the iframe, but the display is still useful; MSIE has some oddities but overall works). The settings page has a new option to control SWFPut video in the editor: always, only non-mobile, or never. If the video display feature is disabled, the shortcode will simply appear in the editor.
  • Overdue improvement to the video control bar: if the display is too narrow for all buttons, then the non-essential fullscreen and natural-scale buttons are hidden.
  • Miscellaneous small fixes.
  • Checked with new WordPress 3.9.

1.0.9

  • Vacated in quantum leap to ring 2 resulting from increased energy state induced by scale of recent changes.

1.0.8

  • HTML5 video support now equals the original flash video support, and a new HTML5 video player provides an interface with the same design as the flash player, and as much of the same behavior as can be implemented with the HTML5 video specification.
  • A new option (on the settings page) to make HTML5 video be primary content, with flash video as fallback. The default is to place flash video as primary content with HTML5 video as fallback due to the burden HTML5 video puts on users to provide several video file formats, but users who are confident in the use of HTML5 video will find this new option preferable.
  • It is not necessary to specify both flash and and html video resources; either can be left out (i.e., SWFPut is no longer a flash video player first with html video as an afterthought).
  • Incompatible change: a checkbox on the setup form to specify that the medium is audio, not video, has been removed. That feature really had no place in this plugin, and audio-only support in the flash player was bare-bones minimal.
  • Interface: when a mobile browser is detected, the control bar removes the natural-scale and full-scale buttons, which do not make sense on mobile. The simpler control bar is more appropriate and usable.
  • Improved help under the "Help" button the editor and widgets pages.
  • Interface: volume control slider now presents vertically on non-mobile, and horizontally on mobile. It now scales down at small display sizes (previously it was clipped).
  • The original design goal that JavaScript will not be necessary so that your site remains useful to visitors with scripting disabled has been retained, albeit with necessary qualification: the html video player requires JavaScript, but where scripting is not available, the default interface and behavior for the HTML5 video element provided by the browser will be present, so all is not lost.
  • The several .swf binaries for control bar sizes are gone, now a single binary simply scales the control bar (which of course was the original intent and meant to be among the first updates, but time flies like a banana).
  • Directory and file file name changes.
  • Bug fixes, of course.

1.0.7

  • Presentation improvements. Display should be well scaled now, at least for themes that handle scaling; e.g., 'viewport' meta element. This improvement should be particularly appreciable with regard to mobile platforms (on which the display was very poor in previous versions), but desktop/notebook machines benefit too when the window is made small. Video widgets place on sidebar should now be resized to sidebar width regardless of user-set dimensions, but on mobile if secondary content is placed below primary content (i.e. sidebar appears below main area) video object will use available space up up to the dimensions set.
  • The original description through version 1.0.6 stated that "SWFPut does not add any JavaScript." That is no longer the case. Video object size adjustments depend on JavaScript, but on non-mobile platforms the display does not depend on script, and if scripts are disabled the video objects will behave as they have through version 1.0.6. On mobile platforms JavaScript is necessary because on those platforms the plugin now builds the elements by script rather than putting out HTML directly. (It is probably uncommon and impractical for scripting to be disabled in mobile browsers.)
  • There is a new input field on the setup forms, just below the dimensions fields. This is to provide a width to use only if a mobile browser is detected; the height is automatically proportional, according to the regular dimensions. This might be useful for widgets placed on the sidebar, because the sidebar might be placed below, rather than beside, the main content. In this case more space might be available, and larger display might be suitable. This feature is disabled with a value of '0' which is the default. Experiment.

1.0.6

  • Added do-nothing index.php to prevent directory listing, as WP does.
  • Made the "Screen Options" tab -> "Section Introductions" checkbox value persistent, if the "Save Settings" button is clicked.
  • Style tweaks and size tweaks (admin) in response to WP 3.8 changes.
  • Checked with WP 3.8: OK.

1.0.5

  • BUG[unimportant]: tested a defined(FOO) (rather than 'FOO'), but PHP handles that common mistake anyway, and it could only matter in the very exceedingly extremely unlikely case that a .mo translation binary for this plugin's text domain has been installed under the WP's WP_LANG_DIR.
  • Added check for naughty direct invocation.
  • Checked (Oct 25 2013) with just-released WP 3.7: OK.

1.0.4

  • Fixed duplicated message on settings page update resulting from unneeded settings_errors() call: this call did not cause a dup from 3.0.1 to 3.3.1 (but was not needed either), but between WP 3.3.1 and 3.5.? some core guard against the duplicate was removed (or broken?).
  • Updated swf object element and added optional alternative img and video (html5) nested elements. Removed classid from object, except when MSIE is in user agent string. (inspired by suggestion from aileenf).
  • Added help tabs.
  • Some code cleanups.

1.0.3

  • Maintenance.
  • Put i18n final code (__() was already present), added make rules to build *.mo using (added) script in new locale dir, added FPO/test en_US.mo, confirmed working with dummy string replacement.
  • Changed Opt* support classes to use display strings borrowed exactly from WP (3.6) core; these classes are not tied to this plugin and should not use its text-domain. Using core strings, they might still get translated (might get translated when the plugin does not -- that is deemed OK).
  • Added is_admin() check in init code to avoid setting admin-only hooks when not needed (and executing associated code); plus a few more specific current_user_can() checks.
  • Increased maximum "attachment" queried when finding suitable media files to present in posts/pages shortcode form.

1.0.2

  • Corrections in (vaguely distinguished) add_(action|filter) calls, according to tag used, checked against WP source (whether do_action() or apply_filters() is invoked for the tag in question).
  • Changed JS unescape() to decodeURIComponent().
  • Removed compiled README.{tty,tt8} from distribution.
  • Changed 'wptexturize' to 'htmlentities' for paths and things that should not be pretty-pretty'd.
  • Changed 'Tags:' in readme.txt (and stable, etc.).

1.0.1

  • Maintenance.
  • Editing and corrections in readme.txt.
  • Behavior change: without initial image ('poster'), medium is no longer fetched automatically (without visitor play); was a misfeature that would simulate an initial image by pausing at a random point within first few seconds of the video, but the unsolicited download is a bad idea. (Might be an option in future.)

1.0.0

  • Initial release.

Requires: 3.0.2 or higher
Compatible up to: 3.9.1
Last Updated: 2014-5-3
Downloads: 1,095

Ratings

0 stars
0 out of 5 stars

Support

Got something to say? Need help?

Compatibility

+
=
Not enough data

0 people say it works.
0 people say it's broken.