as you are a Pro user I checked your site briefly. I see that your theme (Jupiter) is already using fancyBox library which FV Player is using as well. And that is causing the issue, it just reports:
“fancyBox already initialized”
Please switch back to the release version for now and we will ensure FV Player’s fancyBox plays well with other plugins.
I checked this and it’s going to be tricky with the styling, if your theme is bundling the fancyBox styling in it.
But you can check with this new plugin version here: https://github.com/foliovision/fv-wordpress-flowplayer/archive/fancybox-fix.zip Just reinstall the plugin from that ZIP file. To do that you will have to first deactivate and delete the current FV Player plugin you are using. WordPress will warn you that you might loose settings and data, but it’s not the case with out plugin, no settings now videos will be lost. Or you can just replace the plugin files via FTP.
I’ve the same problem. I already use fancybox.
I installed version attached on post above but it’s version 6.6.6 not fixing for 126.96.36.1997.
Another thing I notice is that if I click on upgrade now from version 6.6.6 once clicked I get alert, if I click on ok nothing happen. I did a screenrecording: https://drive.google.com/file/d/1rJ1V-31na40MmcD99EXxRbNQKz1RFjmY/view
Let me know. Thanks
to update FV Player please click the upgrade link with right mouse button and select the option to open the link in new browser tab. There was a nasty bug like that in last version 6 release of FV Player. So we put in a written message suggesting the above as well. You should be seeing it too.
If that won’t fix the issue, please provide a link to the page where we can see the failure.
do you use any other plugin which works with fancyBox?
I tried to reproduce the bug, so I installed some plugins. First it was “ARI Fancy Lightbox”. Once it was activated I was getting “fancyBox already initialized” on console, but the lightbox still worked. The styling was a bit off though. That plugin uses fancyBox 3.2.10 while FV Player has 3.4.1, so that could be the reason for the styling mismatch.
Next I tried to use “Easy FancyBox” alongside FV Player. Not only I saw that message again, but also clicking FV Player didn’t open the lightbox at all. So that’s a problem. It was using fancyBox 1.3.23 which is really outdated – I can see 1.3 versions were released in 2010.
Next, “FancyBox for WordPress” is using fancyBox 1.3.8.
What is the fancyBox script version in your theme? Perhaps FV Player needs to detect other plugins loading fancyBox and prevent it. The last two plugins which I mentioned also seem to load fancyBox in a non-standard way, not using WordPress API which is a problem too.
thank you for your reply and sorry for delay.
I use fancybox ver 2.1.5 (I haven’t updated to the new version yet) in my custom theme and I include it via wp_enqueue_script (I get script on cdnjs).
I use fancy to load course page in overlay. This page include video. I think that style and script loaded from fv crash my site.
I analyzed the code, removed fv script and style and everithing’s fine
Can you add option to disable fancybox? Fancybox is used to load video in overlay and if someone doesn’t need this function, can save bandwidth without loading these 2 extra files (or if someone use older version of fancybox) like Load FV Flowplayer JS everywhere option in integrations/compatibility blocks
What do you think? Iit could be a good idea?
Sorry, no, I’ll try to explain better.
If someone doesn’t need overlay function or if someone use an older version of fancybox, you can add a new option “Disable Fancybox library” in integrations/compatibility block settings so everyone can disable foliovision fancybox loaded library (and use their own).
it you don’t enable Settings -> FV Player -> Sidewide Flowplayer Defaults -> “Use video lightbox for images as well” the fancyBox from FV Player won’t load, unless you are viewing a post with [fvplayer] shortcode which uses the lightbox attribute.
Please check. I don’t see a need for “Disable Fancybox library” checkbox.
I already have this setting disabled but fancybox library are still loaded:
This breaks default fancybox style so, with “Disable Fancybox library”, I can avoid library loading and use fancybox like before.
I’ve “Use video lightbox for images as well” unchecked but “Load FV Flowplayer JS everywhere” checked. I have no lightbox attribute in shortcode.
I do not use fv_fancybox so I would like to check “Disable Fancybox library” to avoid library inclusion and use “standard” plugin option instead of call
wp_dequeue_script( ‘fv_player_lightbox’ );
wp_dequeue_style( ‘fv_player_lightbox’ );
in my custom functions.php.
that is correct use of that setting.
We could add the “Disable Fancybox library” setting, but in general we would like to remove some settings and not add new.
Perhaps the “Load FV Flowplayer JS everywhere” setting could be changed into “Ajax Support” and then enabling that would give you a list of things you would like to support in Ajax loaded FV Player:
* Vimeo videos (load Dash.js)
* HLS videos (load HLS.js)
* Lightbox (load fancyBox)
Or we could improve our code to load these scripts on demand, but that can get tricky.
I will have to check this with Alec.
For now you can keep using that PHP code.
I really dislike the idea of selectively loading scripts. That’s a support nightmare. If a publishers chooses not to use FV Player Video Lightbox (due to their own tastes or a conflict with an out of date Fancybox js), then the publisher only needs to disable the FV Player Video Lightbox.
What I’d like to do on our end, is make it easier to handle these Fancybox issues. There’s no reason for three versions of a single library to load (and every performance reason not to do it), even if with a different prefix.
Martin and I will work on reducing the Fancybox conflicts.
Our plugin is too complicated already. We have to simplify, not make it even more complex.
Thanks though for the detailed notes. Martin will work with you on resolving this Fancybox compatibility issue.
I was looking into this:
* ARI Fancy Lightbox registers the Fancybox script as “ari-fancybox” and it’s version 3.2.10
* Easy FancyBox uses “jquery-fancybox” and it’s version 1.3.23
* FancyBox for WordPress uses “fancybox” and it’s version 1.3.8
For the later two cases it’s impossible to fix. We could only add a code to our plugin which prevents these old versions from loading in order to not break the FV Player lightbox functions. But then it’s hard to guarantee that it these plugins keep working.
It would help if there would be a single popular plugin or theme for which we would have to fix these issues as multiple users would complain about these issues.
I just updated to the new beta and my lightboxes stopped working.
Please check (redacted) homepage (scroll down to ‘our latest films’ – the section with 3 videos in a row)
I’ve disabled all the custom CSS for FV Player.
Help, please. Thank you!