-
Hello,
I work with the Divi Theme. I’m not sure it has anything to do with this. Unfortunately I can’t insert the shortcodes. Is there a workaround for this?
https://cdn.indikator-design.com/media/screen-video/flowplayer-embedding.mp4
Thanks.
-
-
And why does this not work?
flowplayer( ‘div.flowplayer’ ).play().volume( 100 );
–> Uncaught TypeError: Cannot read property ‘play’ of undefined
It is not possible to use the id because it changes on every reload.
How can I add a custom id to div.flowplayer?
And how can the volume in every browser be set to 100% when starting with Autoplay?
Ok, the Uncaught TypeError is solved. You should really work on your developer documentation. It’s extremely confusing.
So the following questions are still there:
1. Embed the shortcode in Divi
2. How can I add a custom id to div.flowplayer?
3. And how can the volume in every browser be set to 100% when starting with Autoplay? For example, in Chrome, it starts quietly. But I know it from other Pllayers that they start with volume, which also makes sense with Autoplay.
This doesn’t seem to solve the volume problem either.
flowplayer(function (api, root)
{setTimeout( () =>
{api.play().volume( 100 );
}, 100 );
api.bind(‘cuepoint’, function( e, api, cue )
{if( cue.time == 5 )
{alert( ‘triggered’ );
}
});
});
Hello Bruno,
I see that he use of player element IDs in our documentation is misleading as the ID changes. Next version of FV Player brings database storage of player configuration, making the fixed IDs possible.
The script which you are creating won’t help – not all browsers like video autoplay. For example Google Chrome will only permit muted autoplay unless you interacted with the video on the website before. You can read more on this topic here: https://foliovision.com/2018/05/video-autoplay-issues
FV Player already handles this properly and if you set a video to autoplay, it will autoplay with sound if it’s permitted, otherwise it will play muted.
The Divi issue will be partly solved with the new FV Player version. There you will be able to create new instances of our player on a dedicated FV Player screen in wp-admin and then only put a simple shortcode like [fvplayer id="54"] where you need it.
FV Player used to work with Divi, I wonder which Divi update could break it. I see it worked with version 3.0.40. There must be some JavaScript error. To obtian that please open your browser console, here’s how: https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis Then load your post editing screen again and see if any error appears on that console. Then insert new FV Player using the FV Player Shortcode Editor and see if anything appears too.
Thanks,
Martin
Hello Martin,
In my case it does not work with the latest version of Divi: 3.17.6.
The volume at autoplay is a real shame. But if the browser providers introduce it more and more, you have to come up with new strategies. Thanks for the feedback.
Hello Bruno,
could you please let us know about what you see on your browser console? Is there any error with FV Player JavaScript, or is the issue related to tiny MCE in Divi? We don’t have a new Divi version at hand.
We are also happy to help you resolving the issue right on your website, just order our pro support: https://foliovision.com/pro-support
You can also just create new FV Player instances on a new page where you won’t use the Divi page builder and then move the shortcode over to your page with Divi on it.
Thanks,
Martin
Ah sorry. No, there are no errors to see: https://cdn.indikator-design.com/media/screen-video/flowplayer-embedding-no-error.mp4
I have sent you a link to a Zip to the new version via support (at) foliovision.com.
Hi Bruno,
Thanks for sending it over. We will have a look. Did the solution
that Martin mentioned above worked for you?Thanks,
Lucia
Hello Lucia,
yes it works on a new page in the dafault text area. So I can use it as a workaround.
Thanks
Hello Bruno,
I was able to fix the Divi compatibility, it’s not really a problem, but there is a lot of things to check, so this will take some more time.
Thanks,
Martin
