[{"name":"SWFPut – SWFlash Put","slug":"swfput","version":"3.1.0.1","author":"Ed Hynan","author_profile":"https://profiles.wordpress.org/edhynan/","requires":"4.3","tested":"5.5.15","requires_php":false,"requires_plugins":[],"rating":0,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"downloaded":7368,"last_updated":"2020-08-12 12:00pm GMT","added":"2013-07-28","homepage":"//agalena.nfshost.com/b1/software/swfput-html5-flash-wordpress-plugin/","sections":{"description":"

SWFPut provides ‘responsive’ video for posts and pages.
\nSWFPut makes the presentation of video reliable for your
\nvisitors: several conditions are handled well, such as
\nthe uneven support for HTML5 video formats in the major
\nbrowsers, the possible lack of support for either HTML5
\nvideo or flash video in the visitor’s browser, and even
\nthe possiblilty that JavaScript might be disabled in your
\nvisitor’s browser.

In addition to video for posts and pages, SWFPut provides
\na video widget for use in widget areas, such as a sidebar.

SWFPut video is ‘responsive’: it should display at a
\nsuitable size on your visitor’s device, whether large
\nor small (a responsive WordPress theme is necessary).

SWFPut makes video setup easy and flexible by providing
\nan easy dialog based setup similar to (and based on)
\nthat used by WordPress core media, and also an
\nadvanced form with additional settings, which
\nappears in a new “metabox”
\non the editor page. For widgets, the form appears with
\nthe usual drag and drop widget interface. After adding
\nvideo objects, the form will continue to be useful for
\nmaking changes (or, if you wish, to delete the video).

In WordPress versions 3.3 and greater, video added by
\nSWFPut will be visible in the post/page visual editor.

As many video objects as you wish can be placed in posts
\npages, and of course the widget supports as many instances
\nas you wish.
\nYou may specify HTML5 or flash video, or both with one
\nbeing primary content and the other as fallback.

Here are some features of SWFPut to consider:

\n
SWFPut works directly with media file
\nURL’s; that is, SWFPut does not embed
\nthe video players of providers such as YouTube or Vimeo.
\nSWFPut is for video files which are accessible by URL,
\nwhether hosted at your site or off-site.
\nThe setup form provides two media selection lists.
\nThe first is a selection of files found (recursively)
\nunder your wp-content/uploads directory. This list
\nhas the advantage that it does not use the
\nWordPress media library — it will find files that
\nyou upload ‘by hand’ (with ftp, ssh, etc.). This feature
\nwill work around upload size limits that might prevent
\nyou from uploading large video files to the media library.
\nThe second is a selection of files found in the
\nWordPress media library and is presented with the
\nfile name and the ‘attachment id’. This refers to files
\nby ID, so it might be helpful if you manipulate media
\nand expect ID associations to be valid. Files selections
\nare filtered by name extension: FLV and MP4 for flash,
\nand MP4, OGG and OGV, and WEBM for HTML5 video.
\n
\n
Video resources do not need to be on your site:
\nany URL can be specified, so you may present players
\nfor off-site of 3rd party resources.
\n
\n
SWFPut does not interfere with the appearance of
\na site: a video is presented jsut as an image
\n(such as .png or .jpg) is, with the same sort of
\nstyle, and optional caption. The appearance of the
\nvideo control interface, or control bar, is simple
\nand quiet so it should not clash with site design.
\n
\n
SWFPut allows you to set the display aspect ratio
\nfor the video. Some video is ‘anamorphic’ in that
\nthe pixel width and height do not match the intended
\nproportion of display width and height. You might
\nfilm your child’s school play as 16:9 ‘widescreen’
\nbut use a space saving feature of your recorder that
\nsaves the video at 480×360 (which is not 16:9). You can
\nset SWFPut to display the video at the intended 16:9
\naspect ratio. You may set any aspect ratio (make it
\ndistorted if you wish).
\n
\n
The core features of the flash video player program
\nincluded with SWFPut have been verified to work with
\nthe Gnash free-software browser plugin, which is good
\nif you care about free/libre software users. (At the
\ntime of this writing, Gnash does not handle the MP4
\nvideo container format, so it is preferable that you
\nprepare flash video in the FLV container, even using the
\nh.264 and AAC codecs. Of course, you may use MP4 if
\nyou must.)
\n
\n
The flash video player program included with SWFPut
\nis written and compiled with the Ming PHP extension,
\nand the code is included, so you may modify the player.
\nThe HTML5 player is written JavaScript, and the original,
\nun-minified version is included, so you may modify it.
\nIn fact, the zip archive available at the WordPress
\nrepository includes all sources, although a POSIX/Unix
\nenvironment with certain tools is required to build.
\n
\n
Localization sources are included; hopefully, polyglot
\nusers will help with translations.
\n

\n","installation":"

There are no special installation requirements.

Preferably, install SWFPut from the WordPress Plugin
\nRepository through the WordPress administrative interface.

To install from a zip archive:

\n
Log in at your WordPress site
\n
\n
Select ‘Plugins -> Add New’
\n
\n
Select ‘Upload’
\n
\n
Select ‘Browse’
\n
\n
In your system’s file selector, select the SWFPut zip file;
\nselect ‘OK’ or equivalent
\n
\n
Select ‘Install Now’
\n
\n
Select ‘Activate Plugin’
\n

At this point “SWFPut” should be an entry on the plugins page.
\nThe Settings menu should have an item “SWFPut Plugin”.

If the above is not so, there is probably a problem at your site’s
\nhost; for example if the host is Unix system there is very likely
\na problem with incorrect permissions metadata (mode) on a directory
\nsuch as wp-content/uploads, or an unsuitable user or group ownership
\nof (probably several) files and directories. This can be a frequent
\nproblem if the host has PHP configured in “safe mode”.

If the host is not a Unix system, I’m sorry to say I cannot help;
\nmaybe your hosting provider can.

If the installation was successful, you should see a “SWFPut Video Player”
\nwidget under ‘Appearance -> Widgets’ and a meta-box entitled
\n“SWFPut Video” on the posts and pages editing pages.

For additional help, you will find README* files (differing in format,
\nand excluding ‘readme.txt’, which is this file) that discuss the
\nflash video player in more detail.

\n","faq":"\n

\nWhat are the privacy implications of using SWFPut\n

None. SWFPut does no tracking at all. No information
\nof any sort is gathered or stored or forwarded to another
\nsite, or any such thing. There is no contact made with
\nany other site(1). These statements apply both to the
\nWordPress user, and to site visitors.

(1) The user can provide a media URL from a 3rd party site
\nwhich a visitor’s browser will load; this ‘contact’ of
\nanother site is entirely up to the WordPress user or administrator.

\nI installed SWFPut, now what?\n

First, note that in the editor page for posts/pages,
\nthere is a new ‘metabox’ named “SWFPut Video.” It
\nmight be near the bottom of the page, but metaboxes
\ncan be moved by dragging with the mouse. (When using
\nSWFPut it might be useful to drag its metabox to
\njust below the editor.) If necessary click the metabox
\ntitle to show the form.

The SWFPut form might look complicated, but don’t
\nworry! There is help. At the top right of the WordPress
\neditor pages there is a tab named (in english)
\n“Help.” Click that, and editor help material will drop
\ndown. SWFPut adds a new tab here called “SWFPut Video”
\n(what else?). Click that tab and . . .

. . . another drop-down, this time specifically
\nfor this plugin. Near the top there are two hyperlinks
\nwhich open in a new tab/page, one for PDF documentation
\nand one for (old-time style) HTML documentation. These
\nare versions of the same detailed document. The remainder
\nof the in-place help text addresses just a few items
\nthat the author (I) thought would need more explanation
\nfor a quick start. Please peruse these for use.

Quickest of all, see the FAQ below entitled
\n“Do I really need video in 3 or 4 formats?” which
\nin spite of the name addresses quick and easy use
\nas well as video formats.

\nDo I really need to understand “aspect ratio” and things?\n

Probably not. In most case the width and height of the
\nvideo will match the intended display proportion.
\n“Anamorphic” video is not rare, but probably not too common
\neither. The author has seen videos on e.g., YouTube,
\nthat are distorted by wrong display aspect ratio
\n(which is not YouTube’s fault), but only a few.
\nIf you find that your video looks squeezed or stretched,
\nyou can always use a little trial & error with the display
\naspect setting until it looks good.

\nDo I really need video in 3 or 4 formats?\n

Possibly not. The help documention included with SWFPut
\ndiscusses file formats for HTML5 and flash with a level
\nof detail that — it is hoped — will help you make your video
\navailable to the broadest range of browsers used by your
\nvisitors. The cost of this detail is the loss of simplicity.

The simplest use with not-too-bad availability would be like this:
\nprepare your video in MP4 format; place the URL in either
\nthe “Flash video URL…” or “HTML5 video URLs…” fields[*]
\nin the setup form, and set display size in the “Pixel Width:”
\nand “x Height:” fields; make sure that the cursor in the
\neditor is at the spot you want, and click the
\n“Place new in post” button. Publish the post/page with
\nthe “Update” button. Not too difficult!

Currently many browsers support MP4 for HTML5 video,
\nbut not all! The flash browser plugin has supported MP4
\nfor a long time, but alternatives such as Gnash
\n(a free-software flash plugin) might not. Availability
\nwill be increased significantly by adding FLV (flash)
\nand OGG (or ‘ogv’, a patent-free, free-licensed type) formats.
\nIf you need video conversion software,
\na quick web search should yield several options.
\nChange the procedure in the above paragraph like this:
\nplace the URL for the FLV type in the “Flash video URL…”
\nfield, place the URL for the MP4 type and
\nthe URL for the OGG type separated by a ‘|’
\nin the “HTML5 video URLs…” field (and don’t worry about
\n‘codec’ types discussed in the help docs). Easy, and fun!

Finally, to cover all the bases, amend the the above paragraph
\nlike this: place the URL for the FLV type in the “Flash video URL…”
\nfield, place the URL for the MP4 type and
\nthe URL for the OGG type and
\nthe URL for the WEBM type separated by a ‘|’
\nbetween each in the “HTML5 video URLs…” field . . . .

[*] MP4 can be placed in either the flash or HTML5
\nURL fields and it will be effective for both, as long
\nas the visitor’s browser has JavaScript enabled.

\nWhat if a visitor has JavaScript disabled?\n

SWFPut is designed with that in mind. If scripting
\nis disabled, but either flash or HTML5 video is
\navailable, then your video should be viewable.
\nHTML5 video will have the browser’s native interface
\nand basic features.

\nHow do contact to the developer?\n

Post a comment at
\n//agalena.nfshost.com/b1/software/swfput-html5-flash-wordpress-plugin/
\nor email edhynan at the email provider ‘gmail’ with the
\ntop level domain ‘com’, or of course go the the SWFPut
\nWordPress page at https://wordpress.org/support/plugin/swfput
\nand select the “Support” tab.

\nDoes the developer want to know I use SWFPut?\n

Yes, the developer would consider it kind of you
\nto leave a comment with the URLs of your using pages.

\n\n","changelog":"

3.1.0

Fix ‘continue’ statement with a ‘switch’ enclosed in a loop.
\nThe statement was missing a level argument, e.g. ‘continue 2’.
\nThis bug had no effect, as the end of the switch block is
\nfollowed immediately by the end of the loop block.

3.0.9

Fix for MS Edge browser.

3.0.8

Fix new mce-view visual editor presentation with WP 4.6.
Widget support for WP 4.5 preview ‘selective refresh’ bug fix: stop play.
Change default for aspect ratio auto adjust to false.

3.0.7

Add widget support for WP 4.5 preview ‘selective refresh’.
Confirmed working with WP 4.5.

3.0.6

Poster image might have been too small after stop button
\nclick; this should be OK now.
Confirmed working with WP 4.4.

3.0.5

Fix for URLs without scheme (e.g. “//www.example.com/foo/”).
Editor button: changed to .
Cleanup minor JS warnings on web console.
Misc. cleanup, source comment edits.

3.0.4

Further improve controls for mobile.

3.0.3

Make controls work in Chrome/Chromium mobile.

3.0.2.1

Same as 3.0.3 (Seems new WP version no longer handles 4th minor
\nrevision number, so 2.1 is now 3).

3.0.2

The just released WordPress 4.2.3 security revision includes
\na change that appeared in WP 4.3beta1. This release of SWFPut
\nadjusts a version check so that the changes of SWFPut 3.0.1
\ntake effect for WordPress 4.2.3.
Fixed bug in new visual editor dialog code that caused changes
\nin the caption field to be lost on switching to another tab.

3.0.1

Fix new mce-view visual editor presentation with WP 4.3beta1.
Fix URL preparation bug in plugin_page_addlink().
Misc. code cleanups.
New .htaccess file.

3.0

\n
This release includes an improvement to the responsive
\nsizing of video: the height of a video is now limited
\nto fit within the visible vertical area. Previously, sizing
\nwas applied to width alone. This change should be
\nmost noticeable on small devices, particularly
\nhandheld devices in landscape orientation. This change
\napplies to desktop browsers too, although it will
\nprobably not be evident unless the browser window
\nis at a small size.
\n
This version has small documentation updates regarding
\nthe new visual editor interface of release 2.9, and
\none bugfix needed because of using a new WP function
\nsignature changed at some point before 4.x — this
\nwould not have affected users of current WordPress,
\nbut SFWPut is still supporting (i.e., working with)
\nWP as old as 3.0.2 (hopefully for no reason, since
\nold versions are probably insecure and should not be
\nused).
\n

2.9

A new interface for adding and configuring videos in the
\nvisual editor. The interface now shares many properties
\nwith the WordPress media interface, and uses much of the
\nnew and maturing core code. Users will find video setup
\neasier, and familiar. The origonal setup form in a
\nmetabox remains available and may be considered an
\nadvanced form, as it retains configuration items that
\nwill not be added to the new simplified interface.
\nThe new interface is only available for WordPress 4.x,
\nand support for 4.0 and 4.1 might be removed in the future
\n(users are advised to keep WordPress up to date).

2.2.2.1

\n
Sigh. Just added a forgotten file (from 2.2.2). The default
\nvideo (mentioned in the 2.2.2 entry, below) would be
\nmissing, because I neglected to ‘svn add’ it. Simple
\nmistake updating the repository.
\n
This should not affect any but those who might try
\nusing a URL that SWFPut rejects. Upgrade at your
\nconvenience.
\n

2.2.2

\n
Bug fix release in response to a kind user query.
\nURLs provided for video files are checked before they
\nare used (good), but elsewhere in code an array key
\nwould be missing if the URL was rejected (bad), possibly
\nleading to PHP error messages appearing on page.
\n
Now, if a faulty URL is rejected, a default video URL
\nis used, linking to a small video that says “OOPS […]”
\nand which should get the site owners attention (site
\nvisitors should find the default video inoffensive, even
\nif unexpected).
\n

2.2.1

Confirmed working with WP 4.1.

2.2

Added long overdue alignment options.
Added video preload option. Before now, the video element was always
\ngiven preload=”none”. Now, the specification values “none”,
\n“metadata”, and “auto” may be selected, or one special option
\nnamed (in english) “per initial image”, which will use “none”
\nif if an initial image (poster) is set, or else “metadata” so
\nthat the browser may display a frame of video as a poster.
\nNOTE: the new default is “per initial image” which will
\nchange the behavior of existing videos that do not have
\nan initial image (or ‘poster’): they will now have the
\npreload=”metadata” attribute, so the browser will make a
\nsmall unsolicited fetch from the server, and might display
\na frame. If that is unwanted, the preload option should
\nbe set to “none.”
Some code cleanups and reorganization.
Check with WordPress 4.0: OK. (Actually, WordPress 4.0-beta3,
\nand in the unlikely event that a problem arises with the
\nreal WP 4.0 release, it will be addressed in a minor revision.)

2.1.1

This release is called “Sigh” and its only change is a
\nworkaround for a chromium 3.4 bug — not on the front end, but
\nin the Visual editor plugin. You want details, you say? OK:
\nthis plugin’s video in the tinymce visual editor is housed
\nin an iframe element. The iframe was given, for principle only,
\na sandbox attribute (with the “allow-scripts” argument), even
\nthought the content is generated by a plugin script and is a
\nknown quantity. This worked in the major browsers including the
\nChromium 22 and 3.[123] tested with, but Chromium 3.4 would
\nno longer run scripts in the iframe. Persons-of-curiosity may
\nweb search ‘chromium iframe scripts’ and see at a glance that
\nChromium has dithered on this subject. Bottom line: the sandbox
\nattribute is removed. Apologies for this release so soon after
\n2.1 a few days ago.

2.1

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

2.0

Video will now display in the TinyMCE “Visual” editor. This
\nrequires HTML5 compatible video files, and a recent and
\nnot-too-buggy browser (Chromium is fine on GNU/Linux, but
\nas on MS it might not run the script in the iframe,
\nbut the display is still useful; MSIE has some oddities but
\noverall works). The settings page has a new option to control
\nSWFPut video in the editor: always, only non-mobile, or
\nnever. If the video display feature is disabled, the
\nshortcode will simply appear in the editor.
Overdue improvement to the video control bar: if the display
\nis too narrow for all buttons, then the non-essential
\nfullscreen 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
\nenergy state induced by scale of recent changes.

1.0.8

HTML5 video support now equals the original flash video support, and
\na new HTML5 video player provides an interface with the same
\ndesign as the flash player, and as much of the same behavior
\nas can be implemented with the HTML5 video specification.
A new option (on the settings page) to make HTML5 video be primary
\ncontent, with flash video as fallback. The default is to place
\nflash video as primary content with HTML5 video as fallback due
\nto the burden HTML5 video puts on users to provide several
\nvideo file formats, but users who are confident in the use
\nof HTML5 video will find this new option preferable.
It is not necessary to specify both flash and and html video
\nresources; either can be left out (i.e., SWFPut is no longer
\na flash video player first with html video as an afterthought).
Incompatible change: a checkbox on the setup form to specify that
\nthe medium is audio, not video, has been removed. That feature
\nreally had no place in this plugin, and audio-only support in
\nthe flash player was bare-bones minimal.
Interface: when a mobile browser is detected, the control bar
\nremoves the natural-scale and full-scale buttons, which do
\nnot make sense on mobile. The simpler control bar is more
\nappropriate and usable.
Improved help under the “Help” button the editor and widgets pages.
Interface: volume control slider now presents vertically on
\nnon-mobile, and horizontally on mobile. It now scales down
\nat small display sizes (previously it was clipped).
The original design goal that JavaScript will not be necessary so
\nthat your site remains useful to visitors with scripting
\ndisabled has been retained, albeit with necessary qualification:
\nthe html video player requires JavaScript, but where scripting
\nis not available, the default interface and behavior for the
\nHTML5 video element provided by the browser will be present,
\nso all is not lost.
The several .swf binaries for control bar sizes are gone, now
\na single binary simply scales the control bar (which of course
\nwas the original intent and meant to be among the first
\nupdates, 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,
\nat least for themes that handle scaling; e.g., ‘viewport’
\nmeta element. This improvement should be particularly
\nappreciable with regard to mobile platforms (on which the
\ndisplay was very poor in previous versions), but desktop/notebook
\nmachines benefit too when the window is made small. Video
\nwidgets place on sidebar should now be resized to sidebar
\nwidth regardless of user-set dimensions, but on mobile if
\nsecondary content is placed below primary content (i.e.
\nsidebar appears below main area) video object will use
\navailable space up up to the dimensions set.
The original description through version 1.0.6 stated that
\n“SWFPut does not add any JavaScript.” That is no longer
\nthe case. Video object size adjustments depend on JavaScript,
\nbut on non-mobile platforms the display does not depend on
\nscript, and if scripts are disabled the video objects will
\nbehave as they have through version 1.0.6. On mobile platforms
\nJavaScript is necessary because on those platforms the plugin now
\nbuilds the elements by script rather than putting out HTML
\ndirectly. (It is probably uncommon and impractical for
\nscripting to be disabled in mobile browsers.)
There is a new input field on the setup forms, just below the
\ndimensions fields. This is to provide a width to use only
\nif a mobile browser is detected; the height is automatically
\nproportional, according to the regular dimensions. This might
\nbe useful for widgets placed on the sidebar, because the
\nsidebar might be placed below, rather than beside, the main
\ncontent. In this case more space might be available, and
\nlarger display might be suitable. This feature is disabled
\nwith 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
\nvalue 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’),
\nbut PHP handles that common mistake anyway, and
\nit could only matter in the very exceedingly extremely unlikely
\ncase that a .mo translation binary for this plugin’s
\ntext 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
\nunneeded settings_errors() call: this call did not cause a dup
\nfrom 3.0.1 to 3.3.1 (but was not needed either), but between
\nWP 3.3.1 and 3.5.? some core guard against the duplicate was
\nremoved (or broken?).
Updated swf object element and added optional alternative
\nimg and video (html5) nested elements. Removed classid from
\nobject, except when MSIE is in user agent string. (inspired
\nby suggestion from aileenf).
Added help tabs.
Some code cleanups.

1.0.3

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

1.0.2

Corrections in (vaguely distinguished)
\nadd_(action|filter) calls, according to tag used, checked against
\nWP source (whether do_action() or apply_filters() is invoked
\nfor 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
\nshould 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
\nlonger fetched automatically (without visitor play); was a
\nmisfeature that would simulate an initial image by pausing
\nat a random point within first few seconds of the video, but
\nthe unsolicited download is a bad idea. (Might be an option
\nin future.)

1.0.0

Initial release.

\n","screenshots":"

$\"<p>The$
The SWFPut widget setup form (bottom).
$\"<p>The$
The SWFPut posts/page setup setup details dialog.
$\"<p>The$
The appearance of video placed by SWFPut (Twentyeleven theme\nwith dark custom colors, sidebar on left), not yet playing.

"},"short_description":"SWFPut provides video players for posts and pages and widget areas, as both HTML5 and flash video.","download_link":"https://downloads.wordpress.org/plugin/swfput.3.1.0.1.zip","screenshots":{"1":{"src":"https://ps.w.org/swfput/assets/screenshot-1.png?rev=750259","caption":"

The SWFPut widget setup form (bottom).

"},"2":{"src":"https://ps.w.org/swfput/assets/screenshot-2.png?rev=1146360","caption":"

The SWFPut posts/page setup setup details dialog.

"},"3":{"src":"https://ps.w.org/swfput/assets/screenshot-3.png?rev=750259","caption":"

The appearance of video placed by SWFPut (Twentyeleven theme\nwith dark custom colors, sidebar on left), not yet playing.

"}},"tags":{"flash-video":"FLASH video","graphics":"graphics","html5-video":"HTML5 video","video":"video","video-player":"video player"},"versions":{"1.0":"https://downloads.wordpress.org/plugin/swfput.1.0.zip","1.0.1":"https://downloads.wordpress.org/plugin/swfput.1.0.1.zip","1.0.2":"https://downloads.wordpress.org/plugin/swfput.1.0.2.zip","1.0.3":"https://downloads.wordpress.org/plugin/swfput.1.0.3.zip","1.0.4":"https://downloads.wordpress.org/plugin/swfput.1.0.4.zip","1.0.5":"https://downloads.wordpress.org/plugin/swfput.1.0.5.zip","1.0.6":"https://downloads.wordpress.org/plugin/swfput.1.0.6.zip","1.0.7":"https://downloads.wordpress.org/plugin/swfput.1.0.7.zip","1.0.8":"https://downloads.wordpress.org/plugin/swfput.1.0.8.zip","2.0":"https://downloads.wordpress.org/plugin/swfput.2.0.zip","2.1":"https://downloads.wordpress.org/plugin/swfput.2.1.zip","2.1.1":"https://downloads.wordpress.org/plugin/swfput.2.1.1.zip","2.2":"https://downloads.wordpress.org/plugin/swfput.2.2.zip","2.2.2":"https://downloads.wordpress.org/plugin/swfput.2.2.2.zip","2.2.2.1":"https://downloads.wordpress.org/plugin/swfput.2.2.2.1.zip","2.9":"https://downloads.wordpress.org/plugin/swfput.2.9.zip","3.0":"https://downloads.wordpress.org/plugin/swfput.3.0.zip","3.0.1":"https://downloads.wordpress.org/plugin/swfput.3.0.1.zip","3.0.2":"https://downloads.wordpress.org/plugin/swfput.3.0.2.zip","3.0.2.1":"https://downloads.wordpress.org/plugin/swfput.3.0.2.1.zip","3.0.3":"https://downloads.wordpress.org/plugin/swfput.3.0.3.zip","3.0.4":"https://downloads.wordpress.org/plugin/swfput.3.0.4.zip","3.0.5":"https://downloads.wordpress.org/plugin/swfput.3.0.5.zip","3.0.6":"https://downloads.wordpress.org/plugin/swfput.3.0.6.zip","3.0.7":"https://downloads.wordpress.org/plugin/swfput.3.0.7.zip","3.0.8":"https://downloads.wordpress.org/plugin/swfput.3.0.8.zip","3.0.9":"https://downloads.wordpress.org/plugin/swfput.3.0.9.zip","3.1.0":"https://downloads.wordpress.org/plugin/swfput.3.1.0.zip","3.1.0.1":"https://downloads.wordpress.org/plugin/swfput.3.1.0.1.zip","trunk":"https://downloads.wordpress.org/plugin/swfput.zip"},"donate_link":"https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=4Q2Y8ZUG8HXLC","icons":{"1x":"https://ps.w.org/swfput/assets/icon.svg?rev=970797","svg":"https://ps.w.org/swfput/assets/icon.svg?rev=970797"}},{"name":"WP FPO","slug":"wp-fpo","version":"1.0","author":"Husani S. Oakley","author_profile":"https://profiles.wordpress.org/husani/","requires":"3.0.1","tested":"3.6.1","requires_php":false,"requires_plugins":[],"rating":0,"ratings":{"1":0,"2":0,"3":0,"4":0,"5":0},"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"downloaded":984,"last_updated":"2013-10-18 2:54pm GMT","added":"2013-10-18","homepage":"http://github.com/husani/wp-fpo","sections":{"description":"

Create FPO blog posts to help your WordPress design and development process. This plugin creates randomly-generated content (via Markov chains from various sources) and creates for placement only posts. All posts are tagged #wp-fpo so you can easily find and delete them when necessary.

A few generic text sources (Lorem Ipsum, the US Constitution, and MLK’s Letter From A Birmingham Jail) are available for selection.

\n","installation":"

The installation process is the same as all WP plugins:

Download and unzip the plugin file
Upload ‘wp-fpo’ directory to /wp-content/plugins/ directory
Activate the plugin through the ‘Plugins’ menu in WordPress

\n","faq":"

What is this plugin for?

I use WP for lots of skeleton site builds — and the default “hello world” post isn’t enough to build a theme or create a design around. This plugin uses generic text sources to create a user-defined number of fake posts. Simple.

How should I report a bug?

You can submit bugs directly to the GitHub Issues list.

How can I contribute code?

This plugin is hosted on GitHub; pull requests welcome.

\n","changelog":"

1.0

First version

\n"},"short_description":"Automatically create FPO blog posts to help your WordPress design and development process.","download_link":"https://downloads.wordpress.org/plugin/wp-fpo.zip","screenshots":[],"tags":{"for-placement-only":"for placement only","fpo":"fpo","lorem-ipsum":"lorem ipsum"},"versions":[],"donate_link":"","icons":{"default":"https://s.w.org/plugins/geopattern-icon/wp-fpo.svg"}}]

fpo

SWFPut – SWFlash Put

WP FPO

Get New Themes & Resources