Incompatible Plugins and Scripts

We do our best to avoid any compatibility issues and fix any which come up, but FV Player is a very powerful piece of software and there are a few plugins which do not play well with others. Here’s an up to date list (including when compatibility issues were resolved).

Fixed

• All In One WP Security (this plugin restricts a lot of files using .htaccess, just remove the “RedirectMatch 403 @” rule, otherwise retina player graphics won’t work)
• bbPress (issues with some templates, version 2.1.41)
• JetPack (issues with After The Deadline module, version 2.1.17)
• NextGen Gallery (reported here, fixed in 2.2.8)
• OptimizePress 2 template (more information)
• Popup Domination (contains older version of Flowplayer )
• SI CAPTCHA Anti-Spam (reported here, fixed in 2.2.8)
• Toolset Types – Colorbox JavaScript library was being loaded twice on the same post editing page causing our shortcode editor to break
• WPLMS Learning Management – check this guide posted by VibeThemes – Compatibility with FV Flowplayer plugin, however playlist and other advanced features still won’t work with WPLMS Ajax loaded content
• WP Lightbox Ultimate - enable Settings -> FV Player -> Integrations/Compatibility -> “Load FV Flowplayer JS everywhere” and it should be able to coexist. If you notice any issues please try to disable the General Settings -> “Enable jQuery” setting in WP Lightbox Ultimate.

Pending

• Hide My WP (one of our user complained about some playlist issues – the item URLs were somehow changed by this plugin, but exact nature of this bug remains unknown as it’s a paid plugin and we haven’t heard back from the user)
• Incapsula Sitelock – as a quick fix enable Settings > FV Player > Integrations/Compatibility > Disable saving of color settings into a static file.
• OptimizePress template version 1 (see FAQ for workaround)
• Photo Gallery (version 1.1.8 – issues when exiting full screen view)
• RokSprocket (conflict between the included MooTools library and FV Player, which causes the page content to load into the player container and totally breaks the playback). There is a fix:
  

  Solved by performing a custom build of the Mootools lib, removing the package “Request.HTML”: Mootools adds some methods to the Element prototype (sic), especially a “load” method. This methods conflicts with FV Player when it fires a load event using jQuery.

• Widgetkit (by YOOtheme) – make sure you configure Widgetkit > Media Player to not handle video tags
• WPLMS Theme (Vibe Course Module plugin) – if you see FV Flowplayer appearing on top of the Mediaelement player check if you have the “Vibe Course Module” plugin installed.  There is vibe-course-module/includes/js/course.js  file which is initializing MediaElement player. It does so for every video or audio element. As a workaround you can fix it by replacing lines (there are multiple occurrences):

  $('audio,video').mediaelementplayer();

  with:

  $('audio,video').each( function() {
    if($(this).parents('.flowplayer').length) return;
    $(this).mediaelementplayer()
  } );

• YouTube WordPress plugin - it’s hooking to all YouTube events, thus breaking YouTube videos inserted using FV Player Pro
• Playback issues for Vimeo videos on Firefox 48 and older versions of Firefox – an issue with playback on certain Vimeo hosted videos on older versions of Firefox(48 and older)

General Plugin Recommendations

While you are looking for incompatible plugins, we recommend taking a look at WPEngine’s plugin blacklist as anything on their list is probably very bad for performance/hosting.

In terms of caching plugins, we strongly recommend Hyper Cache (version 2) as its performance is best of breed (ahead or within 3% of leader depending on your site) without all the maintenance headaches the other caching plugins bring on. For WPEngine you don’t need to run a caching plugin of your own as they’ve set it up themselves.