JW Player Plugins: Deprecated Plugin Functionality

While JW5 attempts to be as backwards-compatible as possible with respect to plugins and skins, certain techniques are no longer available to plugin developers. While these techniques were never officially supported in 4.x, they nevertheless worked in most versions of the player. Plugin developers who wish to update their 4.x plugins for use in 5.0's compatibility mode should read this article and adjust their plugins accordingly.

view.config

• When 4.x plugins call view.config in 5.0, the object returned is a copy of the player's PlayerConfig object. Modifying this copy will have no effect on the player itself. For example, if the plugin attempts to turn on or off autostart in the player, this will not work.

Manipulating the player's display stack

• Plugin developers could use view.skin to refer to the player's display stack. This method is not supported in JW5's plugin compatibility mode.

Modifying view.playlist

• When a 4.x plugin calls view.playlist in 5.0, the array that's returned is only a copy of the Playlist object. Therefore, any changes made to this array will be ignored by the player.