-
I have found that when I use this feature, Vimeo doesn’t count the video’s play numbers. It only counts them when I put the 3rd party player source URL from Vimeo into FV player. I think this is also true of YouTube videos embedded with FV Player. Any thoughts?
-
-
Hello Tim,
I reposted your question here. We are having a look, I wouldn’t expect the 3rd party Vimeo Pro file URLs would work with Vimeo stats.
Thanks,
Martin
Thanks Martin.
Yeah, since using your player I’ve always used the source URL that vimeo provides for 3rd party players and stats have always worked. But using the Vimeo Video’s page URL gives me no stats at all.
Hello Tim,
we tested this and it’s true – the Vimeo Pro file URLs work with the stats, strangely enough.
You can use Google Analytics to see detailed video playback stats though: https://foliovision.com/2015/04/detailed-google-analytics
Thanks,
Martin
Hi guys. I know it’s been a while but I just wanted to check in to see if this has been addressed. As a reminder, when I use the VimeoPro URL as the source for the video player, it doesn’t get counted in Vimeo’s stats. If I use the URL that vimeo provides for 3rd party players (either HD or SD) that DOES get counted in their stats.
It’s a lot simpler to just put in the VimeoPro’s video URL but I need it to be measured in Vimeo’s stats. Will that feature ever work? I’m trying to avoid using Google Analytics. Also, just curious, do you know when you’ll be using the FLowplayer 6 engine? I read a couple of your blog posts and wanted to ask personally.
Thanks for your help, and for all the work you do. Your player continues to be incredible.
Tim
Hi Tim,
We have some good news for you.
Vimeo has released an API for their video files for Pro users. We will add support very shortly (so you’ll continue to be able to just use the http video number but we’ll pull the stat counting links for pro users).
We are also planning some very basic stats (complex stats will slow page loads and add load to the server) very soon, in the back end for you to be able to use. Right now we have planned:
* video page loads
* video plays initiated
* shares initiatedFlowplayer 6 is already built and is about to be deployed later this week (it’s in beta deployment if you’d like to download it and manually install). Martin will post the download link to the top of this post for people who want to try it https://foliovision.com/2015/06/flowplayer-6-bugs
Making the web work for you, Alec
Hello Tim,
I added a note about FV Flowplayer 6: https://foliovision.com/2015/06/flowplayer-6-bugs
Make sure you contact us to get access to beta version of FV Player Pro compatible with FV Flowplayer 6 as the old version of FV Player Pro won’t work if you want to use it though.
Thanks,
Martin
Okay so this is me contacting you for the FV Player Pro extension pack. I don’t know how else to contact you for it.
By the way, thank you Martin and Alec for the response and the positive news about the Vimeo ratings/api, and the update on the next version of your player. I think in my excitement I rushed to download it and forgot my manners lol. Thanks a lot.
Tim
Hello Tim,
I marked your user as a beta tester, so you can get FV Player Pro Beta (for FV Flowplayer 6) from https://foliovision.com/login -> My Products -> Extensions -> FV Player Pro -> (beta). Use it only if you use FV Flowplayer 6 from the article which I posted above.
Thanks,
Martin
Getting this error in my Dashboard:
“Warning: include(/home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/../view/frontend-head.php) [function.include]: failed to open stream: No such file or directory in /home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/backend.php on line 75Warning: include() [function.include]: Failed opening ‘/home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/../view/frontend-head.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/backend.php on line 75″
Also, in my network admin dashboard:
“Fatal error: Cannot redeclare class FV_Player_Pro in /home/vericast/public_html/wp-content/plugins/fv-player-pro-beta/fv-player-pro.php on line 2336”The pro extension is not working. The pro features appear in my site dashboard, but they aren’t showing up in the player. For example, I have no lightbox at all now.
UPDATE:
I have it working (sort of). Videos are playing, lightbox is loading. But for some reason I’m still seeing the “FV Flowplayer” watermark, even thought he flow player pro pack is installed and serialized.I still have this error message in my main site’s dashboard;
“Warning: include(/home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/../view/frontend-head.php) [function.include]: failed to open stream: No such file or directory in /home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/backend.php on line 75Warning: include() [function.include]: Failed opening ‘/home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/../view/frontend-head.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/vericast/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/backend.php on line 75″
BUT I no longer have an error message in my network’s dashboard (I’m using multi site wordpress).
HOWEVER when I click “Check template” in the FV Player settings panel I get this message:
“jQuery library http://img.vericast.net/wp-includes/js/jquery/jquery.js?ver=1.11.2 found, but unable to check version, please make sure it’s at least 1.7.1.”AND..
“Template checker has changed. Just open any of your videos on your site and see if you get a red warning message about JavaScript not working.
FV Flowplayer script found: http://img.vericast.net/wp-content/plugins/fv-wordpress-flowplayer/flowplayer/fv-flowplayer.min.js?ver=6.0.2.1!”I have confirmed that videos are working, and the lightbox is working. I don’t get a red warning message.
Also, regarding the lightbox, the white border is not present in this beta version, so that problem is settled for now.
Actually, new update…new error message: Fatal error: Cannot redeclare class FV_Player_Pro in /home/vericast/public_html/wp-content/plugins/fv-player-pro/fv-player-pro.php on line 2514
I’m giving up on this beta now.
Hello Tim,
sorry about all the trouble.
1) The error message about view/frontend-head.php – fixed, I put up the new version into beta plugin updates and also to the ZIP file in the article.
2) You have to disable FV Player Pro before enabling FV Player Pro beta.
3) You can see logo as Flowplayer 6 requires a different key than version 5. We handle this automatically for our licensed users or you get a warning on the plugin update if you haven’t enabled this.
I’ll send you your license key for FV Flowplayer 6 in email now.
Thanks,
Martin
Hello Tim,
FV WordPress Flowplayer 6 is out. You should be able to upgrade your beta version to 6.0.3, then you will be back on the WordPress.org update system – not beta version anymore.
FV Player Pro needs to be updated to version 0.5. If you don’t see that right away, please try to reactivate the FV Player Pro (it will re-check the license) or get a copy from https://foliovision.com/login -> My Products -> Extension -> FV Player Pro.
Please let us know if there are any issues.
Thanks,
Martin
Thanks Martin. I have updated the plugin, and I have re-downloaded the Pro extension from my “My Products” page, but the settings page says “FV WordPress Flowplayer: Your pro extension is intalled, but it’s not compatible with FV Flowplayer 6! Make sure you upgrade your FV Player Pro to version 0.5 or above.”
I downloaded what was available in my “My Products” page, but I Have no idea if that’s the most recent Pro extension.
Tim
UPDATE
Martin: I was able to sort it out by starting clean with the last public release that I had backed up. From there I did the upgrades of the player, and then the pro-pack via the WordPress back end. I then went back to find the latest license code you guys sent me on July 30th. Everything seems to be up to date and working now.Also the back end says “Pro pack not installed. Please install it and enter your FV Flowplayer license”. But I remember it did this in the past, too, with a previous public release, even though the pro pack WAS installed and serialized. After a day or 2 the message just went away. So we don’t have to worry about that for now. Just wanted to bring it to your attention.
One last thing, in the WordPress Plugins back end the description for FV WordPress FLowplayer says “Uses Flowplayer 5”. not FLowplayer 6. I’m sure it’s probably just a mistake but I wanted to let you know in case you guys need to re-write the public description to indicate “Flowplayer 6″…if it is indeed just a mistake. Just pointing it out as a courtesy; it isn’t a problem for me.
Thanks again for everything
Tim
Hello Tim,
please deactivate, delete and reinstall FV WordPress Flowplayer (use the version from WordPress.org). There was a typo in the FV Player Pro checking routine – if you have FV Player Pro 0.5, then you have the required version.
If you don’t see that update right away, please try to reactivate the FV Player Pro (it will re-check the license) or get a copy from https://foliovision.com/login -> My Products -> Extension -> FV Player Pro.
Thanks,
Martin
Hello Tim,
sorry about the upgrade hassle.
Are you sure you have cleared your CDN cache?
Thanks,
Martin
Don’t be sorry. This is the nature of doing betas; sometimes there are complications. I’m grateful to you guys for including me.
I purged the player, the pro extension, and my theme’s style.css file from the CDN, and my CDN purges instantly so I don’t think that’s the problem.
Hello Tim,
I’m pretty sure your CDN is the issue here.
Looking at the script file on your CDN, I can see the old FV Player Pro script: http://vcmedia.cachefly.net/wp-content/plugins/fv-player-pro/js/fv_player_pro.min.js?ver=0.5
Looking at the script on your site, I can see the new file: /wp-content/plugins/fv-player-pro/js/fv_player_pro.min.js?ver=0.5
I think various CDN services are incredibly popular right now, but it certainly makes the troubleshooting harder – specially if you have issues clearing the CDN cache.
Thanks,
Martin
That’s weird. I purged the whole folder. Maybe I need to purge individual files; maybe purging folders doesn’t work. I’ll purge the file you pointed out here. Thanks a lot. And yes, CDNs do make troubleshooting harder. It adds another layer to consider. Definitely very annoying.
Here’s a little update for you.
I purged the file you indicated. At first it resulted in a weird looking lightbox with no black background or anything…and a play button that wouldn’t go away. So I then removed the custom CSS Viktor sent me from my theme’s CSS file, and purged it. I then purged fv-player-pro/css/style.css. Then I was getting a normal lightbox, but with the border/frame around it like before. I then put Viktor’s custom CSS back in my theme’s style.css file, and purged it from the CDN. The lightbox now loads normally, and without any border around it.
Thank you very much for your time and patience. I still appreciate everything you guys do. I’m a small business myself and I know it’s a pain in the ass to fix issues from a distance. I have to do it frequently too. Have a great day, and thank you again.
Tim
