No more Vimeo Splash images

Hello Cirdec,

please upgrade to FV Player Pro 7.5.5.727 and then use the “Refresh splash screens and durations” button in Settings -> FV Player Pro -> Hosting -> Vimeo.

It should solve the issues unless you use the old [fvplayer src="..." splash="..."] shortcodes. Please let us know.

Thanks,
Martin

Hello Cirdec,

how are you selecting videos with FV Player? If you post a new Vimeo video (or any old Vimeo video again) I see it gets a splash screen like this: https://i.vimeocdn.com/video/708480577-1981ef282c33cba7f73d794fa31f6d06a657535cb965561376c14c79bb729e1d-d_1920x1080?r=pad

It seems Vimeo has changed the URLs for all the splash screens.

If that’s the case we need to roll out an update which will force the update and all the matching splash screen URLs. So you wouldn’t have to click that button which I was mentioning.

Thanks,
Martin

Hello Cirdec,

are you getting broken splash screens even for a new players which you add?

If you can’t really update FV Player Pro right now, then please let us know how do you store the FV Player instances (are you using wp-admin -> FV Player for all videos? Or do you only post Vimeo links? Or do you use full legacy fvplayer shortcodes with splash=”…” argument?) and perhaps we can provide some SQL to let you remove these bad splash screens and let FV Player Pro pick the new ones automatically.

Thanks,
Martin

Hello Cirdec,

please provide the URL of such new video along with the splash screen URL which FV Player is trying to use.

Thanks,
Martin

Update – Had also switched between PHP 7.0 and PHP 7.1.33 prior to refreshing splash screens…now getting an error when trying to back up the site that the WordPress table fv_fp_hls_access_tokens is missing in PHP 7.1.33. Which leads me to believe that’s why the videos won’t play. So it seems that this is more related to how to update PHP without losing the tables required for FV access codes. Any recommendations on how to update PHP while porting over the access-tokens table??

Hello Bethany,

what exact error do you get regarding fv_fp_hls_access_tokens? That table is not used for Vimeo playback.

Is there a page where we can see the video not playing? Please let us know.

Hello Cirdec,

that button “Refresh splash screens and durations” will actually do what they are asking for – it will purge the cached splash screen URLs and FV Player will then fetch the new ones automatically. It already does what’s described in that video.

Thanks,
Martin

Thanks, Martin.

We are seeing this on our site as well, updating and following the steps have not worked. What else can we do to get rid of the color bars and get the splash screens back on our Vimeo content?

Hello Douglas,

please let us know how do you store the FV Player instances. Can you see all of them in wp-admin -> FV Player?

Or do you use bare shortcodes like [fvplayer src="https://vimeo.com/..."] ? Do do you use shortcodes also with the splash argument like [fvplayer src="https://vimeo.com/..." splash="..."] ?

Please let us know what message you get when you click that “Refresh splash screens and durations” button as well.

Hello Cirdec,

please let us know what message you get when you click that “Refresh splash screens and durations” button.

Thanks,
Martin

Hello Cirdec,

the splash screens are added by background processing, that’s why you noticed the issue when logged in at first. Once you reloaded the page it was probably already processed and when you came in not logged in it was already cached as well.

Please check one of your pages built using Elementor – do you see a [fvplayer id="..."] shortcode? You can export that player information by hovering that player ID row in wp-admin -> FV Player and clicking “Export” in the row actions. In the export data you should see there is no “last_video_meta_check” and the splash is empty.

But as I said these splash screens should all appear once the background processing gets to it which might take couple of hours.

Thanks,
Martin

Hello Cirdec,

yes, the export JSON is exactly what I was expecting. It shouldn’t take long before all the Vimeo splash images are processed.

If it seems nothing is happening, please set Settings -> FV Player -> Pro Featured -> Debug to Verbose. That will create a log file where you should see messages like “getting splash for …”.

Thanks,
Martin

We are using shortcodes.

[fvplayer src="https://vimeo.com/{video_id}" playlist="...." caption="...."]

When we press the button to refresh we see:

40 automated Vimeo splash screens removed.
40 Vimeo video durations removed.
40 Vimeo video last_video_meta_check removed.
No cached shortcode Vimeo splash screens found in options!
No cached shortcode Vimeo splash screens found in postmeta!
Back to FV Player Settings

Hello Steve,

do you use that same shortcode format as Douglas?

If the splash image URL is part of the shortcode, it’s not easy for us to update it to a new version of it. I’m going to do some tests now to see what’s the best (and quick) solution.

Thanks,
Martin

Hello Steve,

please start by checking Settings -> FV Player Pro -> Hosting -> Vimeo (Pro). There should be a message like this:

Your Vimeo access token has been successfully verified (last check: {date})

Does it appear?

Next please try to post a new shortcode into a new test post and save it:

[fvplayer src="{vimeo video page link}"]

Will it add a proper splash image that way?

If not, then please enable Settings -> FV Player Pro -> Pro Features -> Debug to Verbose. Then try to post some other Vimeo video and check:

1) Settings -> FV Player Pro -> Hosting -> Vimeo (Pro), there might be a message like this:

There were {number} API errors, last one from {date}.

…with a show link to reveal the errors, please let us know what does it show.

2) If the above is not enough please also check the fv-player-vimeo-….log log file created in the root folder of your website. It should say something about the video which you just posted.

Thanks,
Martin

RE: the token:

Your Vimeo access token has been successfully verified (last check: Fri, 24 Sep 2021 12:59:09 +0000)

And how do we “have a bad shortcocde” when it has been working fine, and the video plays, just no splash screen? That makes no sense.

It is just as you outlined, [fvplayer src="{vimeo video page link}"] (which is what we posted above) except we also have the playlist and caption parameters to the shortcode. And magically ALL of them went bad? Doesn’t seem possible.

I simplified the playlist to just one item…

[fvplayer src="https://vimeo.com/xxxxxxxxx" playlist="https://vimeo.com/xxxxxxxxx,https://i.vimeocdn.com/video/xxxxxxxxx_1280x720.jpg?r=pad;" caption="Testing;testing2"]

I hadn’t noticed before (I did not set these up) that the playlist entries do have the video link, a comma, and a splashscreen. So if that is the cause of the problem, how are those fixed?

The above still shows the splash screen for the main video (maybe because I “created” it when I used it in a solo video tag) but the second one does not.

Deleting the plugin will not delete our settings, will it?

Hello Cirdec,

do these videos belong to the Vimeo account for which you have generated the API key?

How are these videos posted on your website (can it be found in wp-admin -> FV Player, or is that a fvplayer shortcode with src=”…” argument on in the post?)? What’s strange is that these logs show FV Player Pro making 4 requests for these videos at once, as if the internal caching route didn’t work. Or is the video https://vimeo.com/459402231 posted 4 times?

In the meantime we will add processing of Vimeo rate limitting.

Thanks,
Martin

Hello Cirdec,

we have added the rate limit processing into FV Player Pro Beta. Strangely the Vimeo PHP library doesn’t deal with it.

FV Player Pro 7.5.10.727 is out and it fixes the splash caching issue if the player had no splash image stored. That could actually cause some extra calls to Vimeo API which (when combined with the global refresh of the splash screens) could lead to some over-usage.

Please contact Vimeo support if the ban is not lifted in a day from now. They shouldn’t have any problem with removing it as it’s a side-effect of the sudden splash image links change.

Thanks,
Martin

Hello,

I’m in the same case. They asked me lot of information to track the issue. They don’t unban my IP until futher investgation :(.

One question still unanswered because I don’t know how to respond. They ask for the header and body of my requests (which are ban). I enable the debug in the fvplayer and at the root of my website I’ve the log.
But inside I’ve only the reply and not the request.

Is possible to log the request to VIMEO API ?

Thanks for your help
Renaud

Dear Martin,

Thanks for your reply. However VIMEO engineer wants to see not only the URI called (in ma case wp-cron.php) but also the body of the request. The fvplayer debug mode only show me the body of the reply from VIMEO.

Thanks pointing me to the lib you use to contact the Vimeo API. However in fv-playpro/include/vimeo.php I see the release 1.2.6(extract from user agent) which is on github: https://github.com/vimeo/vimeo.php/blob/34a2b06801db3318ebb983821945293773691915/src/Vimeo/Vimeo.php#L35

The latest release seems to have the major number 3… Is it correct ?

If yes, is-it possible tu update the vimeo sdk ?

Thanks for your support

Hi Martin,

I follow your process but when I look into the vimeo.php file I still see the old sdk.

I also try to download the latest version of the pro plugin thru my account, but it’ve the same release number…

Do you have an idea how to log the POST request (curl lib) to permit me to reply to the vimeo support ?