Social setting secure video URL

@rom174 We currently don’t output that tag so I’ve opened an issue for us to add this. You can follow the issue here – https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/2867

Thank you @wpsmort for your fast reply.
Do you think that’s why the video preview is not working when debugging it with the fb tool ?

Just my 2 cents thought, as I don’t know how you are going to handle it, allow me to add this :
Instead of adding a field to the setting screen, maybe the best would be to generate this tag from the existing one and automaticaly replacing the http part of the url with https if not present.

@rom174

1) Please don’t tag me when creating a post. That’s very rude, inconsiderate, and presumptive.
2) If you have comments about features you’d like to see, the best way for you to get it in front of the relevant parties is to post directly to the All in One SEO Pack’s Github repository issue, not on these community forums.
You can participate directly in the development yourself here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/2867

@rom174 Yes, we’d use the current field and output the video URL in both tags. We currently do this for the og:image and og:image:secure_url tags.

As for whether this is why the video preview isn’t working, I doubt that this is the cause. It’s more likely to be that the Facebook debug tool is not cooperating. You may want to change the URL you’re testing by adding /?=aldkjsfh on the end, then Facebook will fetch the page source as if it’s a brand new page.

@hallsofmontezuma 1/ Very far from me to be all you said, it is just the way I say “Hello” to someone… I found your tag in some other topics and was glad to adress my post to a human. Sorry if you felt it this way, it wasn’t the goal at all.
By the way, if I wanted to be rude I wouldn’t even have say hello !
2/ Thank you for the link but it has already been given by your colleague 2 messages above.

@wpsmort Thank you very much

@rom174

I found your tag in some other topics and was glad to adress my post to a human.

Right, and I’m asking you to not do that, because it’s rude, inconsiderate, and presumptive.
Please review the forum guidelines. https://www.ads-software.com/support/guidelines/#the-bad-stuff
Specifically: Do not abuse the @<name> mentions, they are not a tool to get faster responses.

Thank you for the link but it has already been given by your colleague 2 messages above.

If you have comments about features you’d like to see (such as your two cents), the best way for you to get it in front of the relevant parties is to post directly to the All in One SEO Pack’s Github repository issue, not on these community forums.
If you choose to not do that, and to post about development here instead, that’s certainly your choice, but your comments are less likely to be seen by the developers working the issue who aren’t necessarily reading these community forums.

This thread has been closed. There’s no need for further reply.

@hallsofmontezuma

Sorry for tagging you and others before, I won’t do that more now I know it can be perceived like this by susceptible persons.

Let me just add that you are wrong and “presumptive” if you think that my intention was to get faster responses, 2 points that prove it :
– I said “Thank you for your fast reply” because I wasn’t expecting nothing.
– You can find another open topic I started with Hello @<name> more than 2 weeks ago and the plugin author still didn’t answer (maybe because he thinks I am rude, or maybe because he is on vacation, or maybe because…..). As you can see, it’s not because I have no answer that I am harassing him with more posts and tags.

A third point you can’t verify is that :
– I already realised this missing tag in your plugin a long time ago but I decided only yesterday to inform you. You see how fast I needed it to be resolved. By the way, I wonder how you never saw that.

And finally about my “2 cents”, precisely because it is a 2 cents I won’t give this kind of thought on Github where developers know better than me what they have to do. My goal here was to say “For UX purpose, no need to overcharge the screen settings with one more field”. If it ends up on dev side : better, it doesn’t : never mind. I know they will find a solution without me. And in this case, even if they add a field in the setting screen, that’s truly not a problem.