Facebook changed things on there end. See the Jira issue here - http://tracker.vbulletin.com/browse/VBIV-15670 (Note, you must first login to the vbulletin.com forums as a Licensed User before you may see the Jira issue.) It looks like there is a template fix in there.
Mind you - FB changed that one and a half years ago. What really makes me wonder is how vB does not manage to merge such a simple, already provided and time proven fix into a release. This does not take weeks of testing or QA.
Facebook changed things on there end. See the Jira issue here - http://tracker.vbulletin.com/browse/VBIV-15670 (Note, you must first login to the vbulletin.com forums as a Licensed User before you may see the Jira issue.) It looks like there is a template fix in there.
I put the coding in for that issue as you mentioned, even had to disable plugins as directed by the VB tech support which it was already disabled.. still puts in the facebook video link and no video shows. see it here: http://www.jerrylabella.com/forums/s...=6410#post6410
You can change your video url as you add them as Lynn showed it in his comment. Not a perfect fix by any means but the only way I am able to post fb videos.
Quote:
Even with this fix, there are still some facebook videos that will show as a link.
This is a public facebook video - https://www.facebook.com/video.php?v=685455128170995 . When I try to embed it, it shows as a link. If I click to edit the post, it shows this:
[video]https://www.facebook.com/video.php?v=685455128170995[/video]
when what it should be is this:
[video=facebook;685455128170995]https://www.facebook.com/video.php?v=685455128170995[/video]
(and if I modify it to that, then it does work.) So, something isn't working right.
This still seems to be an issue (having to edit the code manually). How can we make it so VB will recognize simply pasting the video link and parse it properly?
Furthermore, all that is displayed is a still image with no "play" icon overlay or anything. If you click it, then the video starts but it's not evident at all. There must be a way to fix this?