-
So, after building out a rather nice website my boss wants to move it to HTTPS to take advantage of the higher SEO signal provided by that protocol. The last issue we are having is that our video backgrounds on our homepage, which are powered by FV Flowplayer and the Flowplayer Pro Pack, don’t play at all. These stream from Vimeo, and have worked fine with http. The only additional errors I’m seeing are two mixed content warnings regarding images loaded by the Flowplayer script.
I have tried fiddling with and then disabling both our minification (BWP Minify) and our caching (W3TC) with no effect on HTTPS. The problem does not appear to reside there. I am on the latest version of FV Flowplayer with a fully-licensed Pro Pack installed.
The website is huemor.rocks; you can load it on http or https to see the difference. The video background on http is Flowplayer; on https Flowplayer doesn’t load and you just get a static image with parallax effects on it. I currently have BWP & W3TC on but I have tested without either and without both to ensure that it is not an integration issue caused by either plugin. I receive no error in the Chrome console; aside from content warnings on loading the play button image we never actually show.
-
-
Hi David,
Thanks for sending in this detailed bug report, including testing. We are on https on Foliovision.com and do use our own player.
Mixing http and https is very tricky so the issue is probably there. We’ll try to take a look tomorrow to give you some pointers. We do have a site launch for a large client so it may be Thursday before we can give you detailed feedback.
Thanks for being part of Foliovision!
Making the web work for you, Alec
Hello David,
please make sure you upgrade to latest FV Player Pro (0.3.8).
If you don’t see an upgrade, just grab a fresh version from https://foliovision.com/login -> My Products -> Extensions -> FV Player Pro. We will check why the update is not pushed to your site.
Thanks,
MartinSo, I got the video to work.
The FV Pro Pack upgrade didn’t fix the problem, though it’s probably good to have both bits upgraded at the same time.
We decided to go HTTPS-only on this site, i.e. 301 all non-HTTPS traffic to HTTPS. As part of this I adjusted the siteurl to HTTPS. The video now plays as it did without security on it; i.e. the problem is resolved. (Thanks for your help anyway.)
So, basically, Flowplayer on HTTPS requires that your site have HTTPS as part of it’s primary Site URL; which matches with the direction the web is going anyway, so I can’t really complain about that. It might be helpful to note that in an FAQ or documentation somewhere for other developers (assuming Google doesn’t just pick up this forum thread).
Hi David,
Thanks for the update. You definitely want the matching pro pack (while there is some compatibility we are not encouraging it, we’re Apple not Microsoft, simple and just works – mixing versions would open up compatibility hell). I agree the world needs to know about the https issue.
Thanks!
