-
Forum Topic: https://wordpress.org/support/topic/how-to-force-fv-videoplayer-to-not-load-fancbox/#post-14123313
I’m going to put what i put in the support topic into this discussion just to keep all information together:
==
I went into the settings of FV Videoplayer, I am on the latest version v7.4.40.727.In Settings -> Setup -> Integrations/Compatibility section, I see the option to Remove fancybox. I have this box checked. I save the changes.
When I go to my site and view page source, I still see FV Videoplayer loading its own version of fancybox.
What is this checkbox doing and why doesn’t it remove fancybox from the site?
I am loading my own version of fancybox.
==
In the Skin setting, i set the margin-bottom to 0px, but that did not seem to make any difference either.
==Martin from Foliovision replied:
that setting servers the purpose of removing the other instance of fancyBox library while keeping what’s in FV Player.
Do you run into this issue on a page with FV Player where the video is set to show in lightbox? Or is the FV Player fancyBox loaded where it shouldn’t be?
For future please use our own support forum to help us keep track of the issues and bug reports: http://foliovision.com/support/
==
And now here we are in the office support forum.
My most recent response starts here:
I’m not sure I understand what you mean about the “other version of fancybox”. What other version? What I was hoping it would do was just not load fancybox from FV Player Pro plugin.
Is that not the case?
What I was seeing was with that option checked, i was seeing fancybox loading from the plugin still. I could not see any change with that box enabled.
Am I wrong or just confused about what the checkbox is supposed to do?
I was able to get rid of your fancybox to not load, but unregistering it via my theme. I changed the name of fancybox id to match what you had in your plugin, so now my version of fancybox in its place. Not ideal, but it worked.
Also the margin-bottom: 0 in the skin settings didn’t take effect, but i was able to override that via CSS. I did have to declare !important to override it though.
Thank you
-
-
Hello crosbymarketing,
the “Remove fancyBox” setting is designd to remove any other fancyBox library used on the website and keeping what’s in FV Player. We currently do not provide it the other way around as we have written some custom handling of fancyBox for FV Player in our script:
– function to get the lightbox title from image alt attribute, or the text in wrapping h5 element or figcaption
– special handling of lightbox thumbnails which represent videos
– show/hide caption bar or info bar only if there is enough space for it
– making the lightbox fullscreen button work with FV Player fullscreen
– stopping video playback on lightbox close properlyIt would be better if we could make our code work with any fancyBox library bundled in your theme or some other plugin. Please post the link to your website where we can see the issue and perhaps we can plan this out. This should work with any fancyBox version 3.
Please also share a link to your page where that bottom margin was not working.
Thanks,
Martinoh ok, thanks for that. I supposed when I read the description it seemed like you were giving the user the ability to turn it off from your plugin. That seemed a bit less intrusive. But I understand now. Makes sense.
Our situation is we are currently using Fancybox v2 throughout our website. Updating to v3, well, it was causing some problems with the areas of the website that use modals. For us, if you can make it compatible with v2, well, that would be great.
For now what I have done is I am not loading fancybox v2 on the homepage of our site and instead I am just letting the FV Videoplayer plugin handle it.
I am loading fancybox v2 in my interior pages throughout the site as that is what is needed there. I am seeing some console errors, so in a future update we will update to v3 of fancybox everywhere. We will get there.
Now i am having a problem with my main domain seeing the license as correct. I’ll open a new ticket for that. I think we can close this ticket here, i figured out some weird workarounds to get it work.
ok and i resolved my license issue too. I just needed to wait about 15mins and now the error is gone.
