By default, Easysocial crawler will trying to retrieve that video whether got og:image tag, if the video provided this, it will import into Easysocial and show this image as video cover.

For example :
[gist type="php"]
// access this source page
view-source:https://vimeo.com/244559084

// og:image they provided
https://i.vimeocdn.com/filter/overlay?src0=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F669460486_1280x720.webp&src1=https%3A%2F%2Ff.vimeocdn.com%2Fimages_v6%2Fshare%2Fplay_icon_overlay.png
[/gist]

[gist type="php"]
// access this source page
view-source:https://vimeo.com/114900089

// og:image they provided
https://i.vimeocdn.com/filter/overlay?src0=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F556340000_1280x720.webp&src1=https%3A%2F%2Ff.vimeocdn.com%2Fimages_v6%2Fshare%2Fplay_icon_overlay.png
[/gist]

[gist type="php"]
// access this source page
view-source:https://vimeo.com/229670574

// og:image they provided
https://i.vimeocdn.com/filter/overlay?src0=https%3A%2F%2Fi.vimeocdn.com%2Fvideo%2F711536792_1280x720.webp&src1=https%3A%2F%2Ff.vimeocdn.com%2Fimages_v6%2Fshare%2Fplay_icon_overlay.png
[/gist]

Hi Arlex

Thank you for your response.
If I understand you correctly you are saying that the “white play button with the black background” is the standard way ES deals with Vimeo?

Going here and here (All videos on these pages are Vimeo) :

https://www.finalbug.net/videos-learn-fcpx-davinci-workflow/categories/11-fcpx-homegrown?start=0

and

https://www.finalbug.net/videos-learn-fcpx-davinci-workflow/categories/11-fcpx-homegrown?start=30

The pattern that I am seeing is that the “white play button with the black background” appears for the first time on links published from the 6th January 2018 onwards!

If I republish some of the same links that I published prior to 6th January 2018 I see the “white play button with the black background”

Eg please see:

Edit NOT Like a Pro 01 take 02
Reposted Test

and

Edit NOT Like a Pro 01

Both published here:

https://www.finalbug.net/videos-learn-fcpx-davinci-workflow/categories/11-fcpx-homegrown?start=0

Also re-editing an old video added previous to 6th January 2018

eg: "Edit NOT Like a Pro 09" results in a “white play button with the black background”

Bottom line I just want to have a consistent look moving forward and can redesign post covers if necessary.

If this is standard ES behaviour I will have to redesign my post covers from here on in.

If this is not standard ES behaviour please help me get to the bottom of this?

kindly advise

Paul

hey Paul,

I would like to clarify one thing is from the older version of Easysocial until now, we doesn't change any crawler behaviour.

The only change is from Vimeo video provider updated their og:image tag to show play button.

Like what you explained above, those old video you added in Easysocial since 6th January 2018, that time og:image tag doesn't include those play button in the cover image.

For example : http://take.ms/W4Wbr
- this video added at 2016, you can see that time they added og:image is this kind of image without included that play button
[gist type="php"]
https://i.vimeocdn.com/video/563199360.jpg?mw=1920&mh=1080&q=70
[/gist]

But this only happen at recently, it might be Vimeo video provider already updated this.

The only way to change this video cover, you have to update your custom video thumbnail image from your video directory folder.

e.g. this video http://take.ms/2phTv , that video id is 408
Go to this directory folder JoomlaFolder/media/com_easysocial/videos/408/..., put your custom thumbnail image over there and make it same name with the original image file.

Hey Arlex

Thank you for your detailed explanation.

And I owe you an apology...

I think I know what the pattern is and I think it is best if Arlex looks at this who kindly helped me with some mission critical Vimeo issues I had.

...for implying that this might have been a side effect of you helping me with my ongoing Vimeo adventure.

Sorry.

Vimeo adding this play button is a pain but not the end of the world.

At least now I understand the pattern and can deal with it appropriately.

thanks as always

Paul

Hey Paul,

Actually no need apologise because i will understand that.

Keep us update if you need any other assistance on this.

Hey Arlex

Thanks again.

best

Paul

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding