Slideshare embed is not responsive

True. But the embed code you have on the page is not the one that was provided by Iframely.

The only way for this to happen is this. In your Iframely options, you have default providers enabled. Before using Iframely shortcode in your post, you entered URL in the editor, and the default WP embed code for SlideShare got cached for this post. It will be in the cache for a day. As Iframely shortcode uses default WP mechanisms, it receives that the default embed code that is already in the cache.

We can not overcome this scenario through the plugin as it would mean implementing embed codes core engine on our own.

This issue is caused by new inline previews since WP 4.0. To fix the problem of this particular post, try the same URL but meaningless query string parameters to it.
Such as

(?refresh=1 added. It’s still the same URL, but WP will treat it as a new one and will re-cache the embed code, this time through Iframely).

Hi Ivan,

Thanks for your reply. I checked that I do not have ‘Do not override default embed providers’ enabled under Settings. I tried added the extra query string parameter to the URL. That didn’t help.

I’m using WP 4.0.1. How else can I fix this?

– Alfred

Hi Alfred,

The good news – I can now see your URLs and API calls in the log. So invalidation of the cache worked that way. The embed code returned should be different and responsive. However, it’s not on your page.

Did you save / publish the blog post with the modified URLs?

If it still doesn’t work, try posting with this short URL: https://iframe.ly/ebbNsj.
This should eliminate any other plugin that might be intercepting in to the process. .

Ivan

Yes, I saved the blog with the modified URL but that didn’t make a difference. However, shortening the URL works! ??

Needing to modify or shorten the URL makes your plugin a little odd to use. I hope you can fix the cache issue in the near future. For now, you may want to add a note in your installation instructions.

Thanks again for your help!

Thanks. And yes, I can see how caching may be an issue when you first install/configure the plugin. Once you get rolling, it should be quite smooth.

For the fix, we’ll wait until WP devs introduce “reload” button for their native inline previews. There reason we are reluctant to mess up with the core is that will cause headaches in maintenance and WP updates. For the users that is ??