Skip to content
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

Closed
2 tasks
ascordato opened this issue Nov 15, 2017 · 13 comments
Closed
2 tasks

Instagram Embed Block #3499

ascordato opened this issue Nov 15, 2017 · 13 comments
Labels
Core REST API Task Task for Core REST API efforts [Type] Bug An existing feature does not function as intended [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.

Comments

@ascordato
Copy link

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)

  1. Add the block to a post
  2. Paste the Instagram URL for the image

I also tried pasting the actual embed code Instagram provides too and the message "Please enter a URL" appears.

Expected Behavior

Current Behavior

screen shot 2017-11-15 at 1 28 54 pm

Possible Solution

Screenshots / Video

Related Issues and/or PRs

Todos

  • Tests
  • Documentation
@aduth
Copy link
Member

aduth commented Nov 15, 2017

Can you share the URL you're using for the embed? I am not able to recreate the issue with a sample URL:

https://www.instagram.com/p/Bbba7EYljLv/

@aduth aduth added [Status] Needs More Info Follow-up required in order to be actionable. [Type] Bug An existing feature does not function as intended labels Nov 15, 2017
@ascordato
Copy link
Author

Here you go: https://www.instagram.com/p/Bbb011mBv5K/

I tried the URL you provided above and got the same error.

@gziolo
Copy link
Member

gziolo commented Nov 16, 2017

I was able to reproduce on ver. 1.7

@hedgefield
Copy link

I was able to embed both URLs successfully on 1.7. They do seem kinda squished horizontally though, but that's another design matter.

@ascordato
Copy link
Author

ascordato commented Nov 16, 2017 via email

@Soean
Copy link
Member

Soean commented Nov 17, 2017

I was able to embed Instagram posts with gutenberg 1.7.

instagram

@GaryJones
Copy link
Member

With GB 1.9.0, it works, but only appears as about 50% width of the content area. Tried with a video and photo.

screenshot 2017-12-12 12 50 57

Aside: The Flickr Embed also seems to suffer from the same symptoms - can't expand to be the width of the rest of the textual content, can't center it within the content area etc.

@clintlalonde
Copy link

clintlalonde commented Jan 2, 2018

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.
image

On self-hosted WordPress 4.9.1 using Guttenberg 1.9.1. Win 10 FF Quantum 57.0.3.

@abdullah1908
Copy link
Contributor

Facing the same issue and tried different Instagram profile URLs but the same result
instagram issue
WordPress 4.9.4
Gutenberg 2.2
Google Chrome 64.0.3282.167

@karmatosed karmatosed removed the [Status] Needs More Info Follow-up required in order to be actionable. label Apr 10, 2018
@aaronjorbin
Copy link
Member

I ran into this issue today.

WordPress: nightly
Guteneberg 2.6: https://www.instagram.com/p/BhR3XVRFSJL/
Chrome: 65.0.3325.181

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 jetpack/modules/shortcodes/instagram.php means that it isn't being picked up by the proxy.

@aduth aduth added the [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes. label Apr 17, 2018
@aduth
Copy link
Member

aduth commented Apr 17, 2018

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 wp_embed_register_handler:

https://github.com/Automattic/jetpack/blob/8a1a92bcfe1b5d4eec671237dd7b85959fccaba3/modules/shortcodes/instagram.php#L62-L63

That said, should the oEmbed proxy endpoint support these patterns as well?

@aaronjorbin
Copy link
Member

@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.

@pento pento added the Core REST API Task Task for Core REST API efforts label Apr 23, 2018
@pento
Copy link
Member

pento commented Apr 23, 2018

We can do this. We have the technology.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core REST API Task Task for Core REST API efforts [Type] Bug An existing feature does not function as intended [Type] Plugin Interoperability Incompatibilities between a specific plugin and the block editor. Close with workaround notes.
Projects
No open projects
Development

No branches or pull requests