I had previously started a thread concerning issues with lightboxes in v6.x of the plugin: https://foliovision.com/support/fv-wordpress-flowplayer/bug-reports/cannot-pass-caption-to-lightbox-when-using-text-links
However since I upgraded to v7, I cannot get a text (link-based) lightbox to correctly open + play, let alone set captions.
I don’t think the docs online have been updated for v7, because the shortcode that the UI creates just doesn’t work.
Can you please give me the exact syntax for a text-based autoplaying lightboxed video for v7?
Hello Twig Interactive,
it works for us here: https://foliovision.com/player/basic-setup/using-lightbox#anchor-text-with-lightbox Check the demo on the “click on this link” link. We didn’t change that shortcode.
If you mean the pure HTML version then that works too: https://foliovision.com/player/basic-setup/using-lightbox#lightbox-without-fvplayer-shortcodes The documentation is correct, we didn’t change the HTML code you need to use to get it.
Perhaps your issue is related to fancyBox conflict. You can read more about it here, I’m linking to the exact post which gives you quick guide about how to troubleshoot the issue with browser console: https://foliovision.com/support/fv-wordpress-flowplayer/troubleshooting/new-lightbox-doesnt-work-on-my-website#post-72977
Sorry for the delay Martin, been busy but now I’m trying to resolve this.
I have a fresh install of WP 4.9.8, running default 2017 theme, with only active plugin being latest FV Player (22.214.171.1247)
You can see from the homepage of the test site that the exact shortcode I copied from your example page doens’t work.
Can you explain what I’m doing wrong? To be clear, I’ve been using FVP for years without issue up to v6.6.6 (lightboxes, embedded, custom captions etc.)
Thanks so much for the assist.
Ah thanks. I don’t have Pro, and we don’t use Vimeo – I just used that directly from your demo site.
I’ve replaced it with local video + splash files; I can see the lightbox pops up now but the video won’t autoplay, even when autoplay=”true” is in the shortcode:
Hello Twig Interactive,
I see that while we decided to autoplay all the lightbox videos starting from FV Player 126.96.36.1997 it doesn’t work for the lightbox text links.
We prepared a fix for that. Could you please reinstall FV Player from this link? https://github.com/foliovision/fv-wordpress-flowplayer/archive/master.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. Then let us know if it all works for you.
Hi Martin – thanks, I can see that the version on the master branch does autoplay lightbox videos. However, it doesn’t look like the autoplay parameter can be controlled via the shortcode, because
[fvplayer src="http://twigpress.aws.twiginteractive.com/wp-content/uploads/2018/10/Sheet-Metal-Straight-Brake.mp4" splash="http://twigpress.aws.twiginteractive.com/wp-content/uploads/2018/10/v-design-mobility.jpg" width="800" height="450" autoplay="false" caption="this is a link" lightbox="true;text"]
still autoplays, despite autoplay=”false”.
Is this intentional?
That’s very helpful. We discourage use of page builders on serious websites. Inevitably they interfere with core functionality and cause publishers no end of issues which would be avoided by building standard template files instead.
Page builders have their uses on experimental sites or small scale sites where a full custom design would be overkill. Even then, I’d recommend buying a good (and simply coded) theme without a built-in page builder. I’ve been building and maintaining WordPRess sites with both modest and millions/views for so long that my view is all about performance and stability.
Anything a publishers to do improve page load speed and reduce maintenance is a long term blessing. Getting rid of page builders is the single biggest possible step in the direction of stability and performance.
Heh I totally agree (I’ve been doing web dev for almost 20 yrs) but sadly, when a client wants “full control” over their site, no amount of fancy theme coding will be enough. All you would end up doing would be to create your own version of a page builder, which wouldn’t be as good (presumably) as one you pay for support on :)
The way we handle it is to build custom admin sections based on templates. It works quite nicely. WordPress is really on the wrong path. Instead of building a better CMS, Mullenweg is chasing the customers around waving Tumbler clones (post types, since retired) and Medium clones (Gutenberg impossible post editing) in their faces like some Pied Piper of Stupidity and Trendiness.
I don’t think in the history of open source there’s been any leader of an important open source project who’s managed to do as much damage to the open source movement as Matt Mullenweg.