-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Instagram Embed Block #3499
Comments
Can you share the URL you're using for the embed? I am not able to recreate the issue with a sample URL: |
Here you go: https://www.instagram.com/p/Bbb011mBv5K/ I tried the URL you provided above and got the same error. |
I was able to reproduce on ver. 1.7 |
I was able to embed both URLs successfully on 1.7. They do seem kinda squished horizontally though, but that's another design matter. |
I just tried again on my end after upgrading to 4.9 and still get the same
error. FWIW, I can get other embed blocks like Youtube to work as expected.
…On Thu, Nov 16, 2017 at 5:25 AM, Tim Hengeveld ***@***.***> wrote:
I was able to embed both URLs successfully on 1.7. They do seem kinda
squished horizontally though, but that's another design matter.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3499 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGmFN_8gFKZJeXTEzBT9Dubz7uXgVZoEks5s3A2HgaJpZM4Qfcol>
.
|
Having same issue. Getting error when trying to embed an Instagram photo. Using my own photo (https://www.instagram.com/p/BX-4fN9Dkcy/) and the test photo given above (https://www.instagram.com/p/Bbba7EYljLv/) gets same results. On self-hosted WordPress 4.9.1 using Guttenberg 1.9.1. Win 10 FF Quantum 57.0.3. |
I ran into this issue today. WordPress: nightly Instagram URL trying to embed: https://www.instagram.com/p/BhR3XVRFSJL/ I've tracked this down to being an issue caused by jetpack. It's removal of the Instagram provider in |
Should we close this in favor of Automattic/jetpack#9331 ? I assume that the plugin should at least leave some oEmbed handler, even if it implements its own alternative. The embed block should work so long as any oEmbed pattern matches. The issue is that Jetpack removes all of them, and only replaces with an That said, should the oEmbed proxy endpoint support these patterns as well? |
@swissspidy and @pento Can likely speak to the oEmbed proxy endpoint the best, but I think it may make sense to fix things up so that this isn't an issue for other plugins in the long run. If that's the case, I think closing this for a core ticket will make the most sense. |
We can do this. We have the technology. |
Fixes #3499. Co-Authored-By: Andrew Duthie <aduth@users.noreply.github.com>
Issue Overview
The embed block for Instagram doesn't work.
Currently running latest version of WP with Gutenberg 1.7 installed. Reproduced this error in Chrome and Safari.
Steps to Reproduce (for bugs)
I also tried pasting the actual embed code Instagram provides too and the message "Please enter a URL" appears.
Expected Behavior
Current Behavior
Possible Solution
Screenshots / Video
Related Issues and/or PRs
Todos
The text was updated successfully, but these errors were encountered: