New lightbox doesn’t work on my website

Hello Ákos,

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.

Thanks,
Martin

Hello Ákos,

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.

Thanks,
Martin

Hello David,

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.

Thanks,
Martin

Hello David,

do you use any other plugin which works with fancyBox?

Do you see any error on the browse console? First open the console according to the instructions here: https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis Then open your page where you can see the issue, try to open lightbox and see if you get any error.

Thanks,
Martin

Hello David,

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.

Thanks,
Martin

Hello David,

do you mean that you are using the “Load FV Flowplayer JS everywhere” settings and want to exclude fancyBox from it?

Are you sure you had to remove both JS and CSS? Isn’t it just the CSS file?

Thanks,
Martin

Hello David,

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.

Thanks,
Martin

Hello David,

if it’s not “Use video lightbox for images as well” nor “Load FV Flowplayer JS everywhere” then there has to be a shortcode with lightbox attribute in it somewhere.

Does it happen even with default WordPress template such as Twenty Seventeen?

Thanks,
Martin

Hello David,

I see, is there any reason why you need to use “Load FV Flowplayer JS everywhere”?

Thanks,
Martin

Hello David,

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.

Thanks,
Martin

Hi David,

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.

Hello Alec,

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

So for the first case we could use the script which that plugin registers as we use version 3.4.1. So it should work, although possibly with some small design glitches as we rely on the newer Fancybox 3.4.1 styling a bit. And then if we do that we still have to stick our JavaScript somewhere – additional JS file – meaning more requests on pageload.

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.

Thanks,
Martin

Hi Akos,

Thanks for the issue report.

I’d suggest you disable the built-in Lightbox in the Jupiter theme. If you’d like us to customize the Jupiter theme for you to disable FancyBox, please pick up a pro support incident and we’d be happy to work with you hands-on to resolve your issue.

Thanks for being part of Foliovision!

Hello Akos,

it’s not clear if you need the theme lightbox functionality or not.

Will enabling Settings -> FV Player -> Integrations/Compatibility -> “Remove fancyBox” (description reads “Use if FV Player lightbox is not working and you see a “fancyBox already initialized” message on JavaScript console”) fix the issue for you?

Thanks,
Martin

Hello Ákos,

we would like to test if FV Player could work with other lightbox plugins out there and not load its own copy of Fancybox library in these cases.

you sent us a link to your staging site privately – the challenge here is that your website uses fancyBox 2 while FV Player is using version 3.

Your theme is also bundling the Fancybox script and so FV Player is not able to remove it, which is too bad, as your photo gallery functions might work just fine with fancyBox 3 provided by FV Player.

Could you please install a new development version of FV Player from this link? https://github.com/foliovision/fv-wordpress-flowplayer/archive/fancybox-2-fallback.zip 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 our plugin, no settings now videos will be lost. Or you can just replace the plugin files via FTP.

That new function supports fallback to fancyBox 2 – so the video lightbox should be working with it on your staging website.

Thanks,
Martin