-
Notifications
You must be signed in to change notification settings - Fork 62
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
Version 2.0: oEmbed Single Entry fails in Gutenberg #981
Comments
Fixes fatal error when embedding in Gutenberg: ![](http://share.gravityview.co/mVCkTL+) Not a problem when running Classic Editor: ![](http://share.gravityview.co/XgCW6W+) Related to #981
@soulseekah This is still failing for me. See the embed on .com.br This should show a single entry: Also, fatal error is back (confirmed on .com.br as well), fixed with 5b1d792. |
Tapping in here works, but it doesn't seem like the right way: https://github.com/WordPress/gutenberg/blob/4dc4c7b7b180ee3aef4c7a9acf40d17501d8bc98/lib/rest-api.php#L99-L137 |
Basically, there's a filter in there called An attempted fix is in 36cb534, should work well. |
That looks like just the thing! |
I love our new API, the solutions themselves are so so simple to write. It does take a lot of time figuring out what to write first, though 🗡️ especially with these weird Gutenberg cases, ugh. Glad to hear it works. |
The Gutenberg code that fails:
UPDATE: Even once that issue is fixed (See #982), the embed isn't rendered—
$_GET['gv_oembed_provider']
isn't being passed, and the renderer doesn't appear to be called in time. Could be related to WordPress/gutenberg#1054 and WordPress/gutenberg#780┆Issue is synchronized with this Asana task
The text was updated successfully, but these errors were encountered: