Ivan Paramonau

Iframely should provide embed codes that work everywhere, including WebViews. The HTML we produce depends on your settings in Iframely account. If you need a hand, please report the issue you’re running into to the support team and we’ll be happy to take a look into what is going on.

Thank you for rating our plugin without trying it. The license description you missed is this:

Iframely is a commercial plugin powered by the Iframely cloud API. Every embed creates a cloud workload, and an active service subscription is required for commercial use or production installations. Otherwise, we offer a free full-featured 30 day trial period so you can give Iframely a try before deciding.

• This reply was modified 1 year, 4 months ago by Ivan Paramonau.

Shortcode comes with no support of the parameters, sorry. You can add the parameters only for all of your embeds via the admin settings page.

We had an idea of supporting the parameters as part of URL’s own query-string. I’ll pass your feedback to the team so we can prioritize it, thank you.

I am revisiting this bug and noticed that I actually could have helped you sooner.

Our API parameters, for a while now, mention it separately – &iframe=1&card=1 – instead of the combined &iframe=card.

So if you configure this way, it should work consistently on the front-end and in Gutenberg.

(notwithstanding, we’re still going to fix the problem with &iframe=card being ignored in Gutengerg)

Thank you for reporting. This is possible because we override your setting with iframe=1 for the Gutenberg editor.

We’ll include a handler with our next update. Cannot share specific plans yet though.

Great, thanks! Your code should work well for the use case.

Hey guys, Ivan from Iframely here (happen to be subscribed to mentions of Iframely).

The issue isn’t AMP-related. Juan, as we figured with you during our debugging, there was a conflict between Iframely plugin and JetPack. JetPack seems to be intercepting Instagram and Facebook outside of oEmbed sandbox, which we didn’t expect.

Here’s the fix that I suggested to you.

We’ll push a new version of the plugin with this fix once we make sure it causes no other issues.

Hey there. Our sizing for vizs should be pretty close to your settings in Tableau itself. Perhaps, the layout changes since the width in your article is limited? Say, if it’s just 600px, the chosen layout will probably be the one you have for mobile devices.

In any case, we’d need to take a look at the exact URL to be able to tell. Please, email to support at iframely.com or post here and we’ll dig deeper.

Thank you.

Description says “Iframely is powered by server API. API Key is required. Get one at iframely.com”.

The service may or may not require a subscription, depending on your use, as described on our site. Plus, there are no limits in the first 30 days upon signup for a key.

Also, the plugin will actually work out-of-the box, with default configuration, and even without API key configured (although you won’t be able to save other settings without a key).

Additionally, you can also self-host the server APIs as described in this support thread.

Therefore, the reason it didn’t work for you is likely one of this:
– Iframely will work only with the new posts out-of-the box. We don’t drop the WordPress cache for older posts upon install (and neither does WordPress by default until after you edit/save a post). See this thread.
– Or Iframely simply couldn’t generate an embed code for your test URL (we require at least an image for general sites to create a summary card. Check how our parsers see your pages at https://iframely.com/debug)

We answer every support request to [email protected]. Usually within 30 mins during business hours. Connecting multiple systems might require patience. With over at least 1900 different systems Iframely connects your WP to – it is worth the effort.

Iframely embeds should work everywhere the oEmbed works in WordPress. That should include the homepage or any list of posts. But that depends on your other settings. Perhaps your theme overrides the default WP config…

Try checking a YouTube video as the only content in the post. If that shows up alright on the homepage, the settings are ok. In that case, please send a link to your homepage with our embeds, we’ll try to take a look what else might be wrong.

Hey, Ivan from Iframely here. I can confirm that you have all relevant information on the page, however our parsers simply cannot connect to your server.

So the problem is not with Yoast.

Rather, there’s an issue with your Apache’s config. It looks your server responds with connection:upgrade (to http/2), regardless of client’s request. That isn’t right. Our parsers make requests over http 1.1 at the moment. If you can’t figure it out on your server – please reach us at [email protected] to debug.

Hi Sander, it should work, though we haven’t tested Iframely with BB press specifically.

BB Press relies on oEmbed features of WordPress – which Iframely extends.

You need to enable embeds for your BBpress first, it seems:
https://codex.bbpress.org/features/auto-embed-links/

Hi, Ivan from Iframely here. Please send a screenshot of your Iframely plugin settings page to [email protected] together with the email address on your account. We’ll take a look into what is going on and remove the block from your account if needed.

For general information for anyone having similar question: the last update in September did take care of WordPress caching. By default, WP refreshes embeds only when you edit/save an article. We added an option to define time-to-live setting for automated cache refresh (= as caching should be). When you activate it, the plugin starts using other cache keys – essentially dropping the previous cache. Because of that, there may indeed be an initial spike in API hits as all older posts refresh.

Hi @hopem22, Ivan from Iframely here. Our plugin isn’t meant to wrap any embeds responsive, just the known providers.

If you need help with generic iFrame and it’s responsive by itself, I’d suggest https://embedresponsively.com where you can enter your iFrame code and get its responsive variant. Then in your WordPress, switch to HTML view and paste the received code there manually.

Hey Nick, so the issue with Giphy was resolved right away, however the older embeds were not updated automatically on your site. In the plugin’s v 0.4.0, the WP embeds caches are resolved and you should be all good now.