-
Notifications
You must be signed in to change notification settings - Fork 810
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vimeo: embed reversal fails with some vimeo URL formats #10529
Comments
As mentioned in Slack, if Core handles all of the cases we're currently handling, we probably should just look to not override oEmbed. We can keep any iframe->shortcode or iframe->URL conversions though. |
As far as I can tell they do, and they also handle the cases above. |
Kicked off a PR for the sake of testing. I would generally trust Core's long-term maintainability of oEmbed's that they support, so want to try first just removing our handler. |
This issue has been marked as stale. This happened because:
No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation. |
Encountered today on a WPCOM Business site with hosting features enabled. Video shows in editor but you get Had to use a different URL such as https://player.vimeo.com/video/xxxxxx and/or the iframe code to resolve. |
Another issue on an AT site. Pasting a Vimeo URL into the block editor would automatically convert into a Vimeo block, but video won't show up on the front end unless the Shortcodes module is turned off. Pasting in the |
Just reminding myself to update the support doc if this gets fixed https://github.com/Automattic/en.support-docs-content/issues/573 |
Got another case on an AT site. Their private showcase only showed up in the front end when the shortcodes module was turned off. |
Noticed this on another site today, 24836304-hc |
Noticed this on another site today, 25275714-HC |
Experienced in 12441064-hc |
Got another case of this here: 26070978-hc Replacing the link structure with |
Had another case of this here; 31463133-hc Replacing the link structure with Note, I can consistently replicate this on an Atomic site. |
Duplicate issue opened in Calypso: Workaround: Deactivate Shortcodes module or use Custom HTML embeds. Internal report and discussion: p9F6qB-7AN-p2 4394244-zd-woothemes |
Also reported in 32373876-hc |
Encountered on 32528438-hc User attempted to embed https://vimeo.com/470165945/df204ef0ec As a workaround, deactivated Shortcode module for now. |
Another case in 4578587-zen Deactivating the shortcodes module did the trick. |
Also reported in 33102724-hc, will let the customer know to use the HTML block to embed the video. |
Fixes #10529 Pulling out IDs from more types of URLs allows them to support more vimeo URL types, such as: * https://vimeo.com/289091934/cd1f466bcc * https://vimeo.com/album/2838732/video/6342264 * https://vimeo.com/6342264 * http://player.vimeo.com/video/18427511
+1 at 4626490-zen |
closing this again, since the problem is fixed in the development version of the plugin. The fix will ship wit the next Jetpack release. |
@ash1eygrace encountered this again on a WPCOM Atomic hosted site today. Toggling off the ExamplePage was using an embed block. The video URL inserted following the https://vimeo.com/XXXXXXXXX format. The editor successfully displayed a working preview of the video.
The editor pulled in Frontend issuesOn the frontend, the page attempts to load
WorkaroundDeactivate the Internal discussion: p1643233702053900/1643232361.051700-slack-C02E26A26CT |
@JoshuaGoode I can't seem to be able to reproduce the issue at the moment. The video in your example seems to be private, and I cannot embed it, whether I use Jetpack or not. Here is how it looks like when I do not use Jetpack: Was the video public yesterday? Any chance you can still reproduce the problem today? |
@jeherve Looking closer, the videos from the recent report utilize domain restrictions on Vimeo's end so they can only be embedded on sites with designated domains. The issue still occurs if we enable the |
That makes sense now, thanks for the extra details. It seems like we'll need to add a Referer header to such requests, as per Vimeo documentation:
|
Not sure if this is the same, but I ran into a simple site today having issues embedding Vimeo as well, here: 138349-hc What Didn't Work
What Did Work
|
4886160-zd-woothemes. I suggested one of the workarounds from the above comment. |
Another report here: https://wordpress.com/forums/topic/problem-z-osadzaniem-video-z-vimeo/
|
Steps to reproduce the issue
All 3 URL formats do work and return an embed in the post editor, since they are valid URL formats and Core's oEmbed method handles them. However, on the frontend of your site only the third video will work: the 2 first ones will only return the following error:
<!-- vimeo error: not a vimeo video -->
We would need to update our embed reversal method to support those URLs as well.
The text was updated successfully, but these errors were encountered: