-
Hi
Here:
https://gtmetrix.com/reports/www.ajibtarin.com/G5sMSc9zI have:
https://i.imgur.com/Z46jyGS.pngIframe_api
Is this loading by your plugin? Because I don’t use youtube at all.
-
-
My developer said This is part of fv_player_pro.min.js file.
How can I stop loading this file? Because in Iran, youtube has been filtered by government and slows extremely the website.
Thanks
Hello Amir,
it should not be loading if there is no YouTube video on the page. I double checked that and it works that way.
However I see it loads on your website as fv_player_pro.youtube JS variable is set to true. Are you using the “Load FV Flowplayer JS everywhere” option? That would explain why it’s loaded – our plugin has no way of knowing if there will be some Ajax call which will require YouTube API to be present.
It could be improved to load YouTube if there is indeed such video during the FV Player initialization process for each player instance (no matter if “Load FV Flowplayer JS everywhere” is enabled or not), but it would take some time to finish that task, as we are working on upgrading to the new Flowplayer 7 core and improving the playlist technology currently.
Thanks,
MartinHi Martin thanks a lot for your help. Yes this option was checked:
Load FV Flowplayer JS everywhereBut in the middle of my testings I noticed none of my videos play.
For example:
https://www.ajibtarin.com/strange-metaphysic/11197
https://i.imgur.com/qGFjtS9.pngHow can I solve this?
Thanks
Hi Amir,
This might be happening because you have restricted access to this video on Vimeo to all domains with the exception of yours but you might set the domain wrong. Could you please check that in the video settings on Vimeo?
Thanks,
EduardHi thanks Eduard for your response. All of these videos were ok but suddenly today I noticed they are not working.
https://i.imgur.com/MAWcIKr.png
Thanks
Hi Amir,
What version of FV Player Pro are you using? The current versions of our plugins are 6.3.3 (FV Player) and 0.8.36 (FV Player Pro), so please check if your plugins are up to date.
Thanks,
EduardYes they are up to date.
I found these all kinds of errors in my error log:
2017/10/05 06:30:12 [error] 29163#29163: *312142 FastCGI sent in stderr: “PHP message: PHP Warning: Missing argument 3 for set_cache_file(), called in /var/www/ajibtarin.com/htdocs/wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php on line 258 and defined in /var/www/ajibtarin.com/htdocs/wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php on line 298
PHP message: PHP Notice: Constant FV_PLAYER_VIMEO_KEY already defined in /var/www/ajibtarin.com/htdocs/wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php(335) : eval()’d code on line 1
PHP message: PHP Notice: unserialize(): Error at offset 74 of 85 bytes in /var/www/ajibtarin.com/htdocs/wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php on line 295
PHP message: PHP Warning: Missing argument 3 for set_cache_file(), called in /var/www/ajibtarin.com/htdocs/wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php on line 258 and defined in /var/www/ajibtarin.com/htdocs/wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php on line 298
PHP message: PHP Warning: Attempt to modify property of non-object in /var/www/ajibtarin.com/htdocs/wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php on line 131” while reading response header from upstream, client: 31.58.252.101, server: ajibtarin.com, request: “POST /wp-content/plugins/fv-player-pro/beta/fv-vimeo-ajax.php HTTP/1.1”, upstream: “fastcgi://unix://run/php/php7.0-fpm.sock:”, host: “www.ajibtarin.com”, referrer: “https://www.ajibtarin.com/one-video/3640/%d8%a7%d9%88%d9%84%db%8c%d9%86-%d8%b9%da%a9%d8%b3-%d9%85%d8%a7%d9%87%db%8c%d8%aa-%d9%86%d9%88%d8%b1/”
Hello Amir,
does it work if you disable the “Turbocharge Ajax Vimeo loading” option? Please let us know.
In the meantime I’m running some tests now.
Thanks,
MartinHi Martin, thanks for your message. I disabled this option and video played successfully. What was the problem?
Hello Amir,
I noticed that your server doesn’t send the protocol in the HTTP_HOST, so it was fixed on the API server to assume https:// and that got it working.
Thanks,
MartinThanks a lot Martin :)
