when I paste a link to one of my own posts directly into an article (oEmbed), the console shows the following error – but only in the backend with the Query Monitor jQuery monitor enabled:
/wp-content/plugins/query-monitor/assets/query-monitor.js?ver=3.16.4 query-monitor.js?ver=3.16.4:788 QM error from JS: QM output does not exist (anonymous) @ query-monitor.js?ver=3.16.4:788 load (anonymous) @ query-monitor.js?ver=3.16.4:752
The plugin itself shows no errors in the admin bar.
When I deactivate the Query Monitor plugin, the error goes away. On the frontend, if I am not logged in, everything works fine, regardless of whether the plugin is active or deactivated.
Anyway – the plugin is great and helpful 
But your plugin has been extremely helpful even without this functionality!
]]>https://datawrapper.dwcdn.net/[UNIQUE STRING]/[NUMBER]/ URLs, but now the share URLs provided are primarily in the format https://www.datawrapper.de/_/[UNIQUE STRING/. This plugin currently only supports the former. To support the latter, all that needs to be added is the following, just after the previous wp_oembed_add_provider() call.
wp_oembed_add_provider( 'https://www.datawrapper.de/_/*', 'https://api.datawrapper.de/v3/oembed', false );Auto Amazon Links has the latest update installed.
]]>The problem is that somedomain.com supports oEmbed (poorly, and we’d rather use our own block). Currently, if someone pastes a URL from somedomain.com into the block editor, it is automatically parsed into an Embed block. We’d like to stop that from happening, and encourage them to use our custom block instead.
How can I tell WordPress to NOT use the available oEmbed for somedomain.com? ]]>
My boss is looking to purchase a solution like yours, but if it doesn’t handle Rumble, that’s a deal-breaker. We are already using expensive plugins that kinda do what need like Dynamic.ooo and EmbedPress which do support Rumble. But we like that your product is all in one and eternally configurable.
This old post from almost 2 years ago indicates support for alternative media like Rumble and Bitchute weren’t top priority, and that is understandable. But, c’mon — its been 2 years already. When can the enthusiastic public who wants to purchase your product expect support for Rumble to be offered? It can’t be that hard to create an integration, speaking as a WordPress developer.
]]>Is there a way to call this really cool block into that function/filter?
]]>Both on Block and Classic Editor, the tweet is no longer rendered as it should when the link is pasted into the editor. The Classic Editor does not give specific errors, while on the Block Editor the error “This content can’t be embedded” is shown. Looking at the requests, I get a 404 error at the oEmbed proxy endpoint. It never happened before the update, so I don’t know what goes wrong. If I try to open that link, I get a 401 error that says that I am not allowed to make such a request from the browser, which should be correct. Existing embeds are not affected and I can still embed the old way, but with oEmbed everything is much quicker.
If you need other info, please let me know! Thank you.
]]>astra_responsive_oembed_wrapper_enable removes oembeds completely (I used another tool for responsive videos). updating is impossible because we use a content blocker (borlabs cookie) for GDPR compliance. the problem started with astra 4.4.0. (there where some changes in the function responsive_oembed_wrapper). had ro rollback to 4.3.1 works fine. so it should be no problem to undo the destructive changes or fix the problems coming with it. thnx
]]>