7 Comments

  1. Michael

    This is great. Take something that was working before and remove it (albeit with good reason) without any fallback – but then add the new version that does work into JetPack to get people to install that bloatware…

    If it’s possible in JetPack, why isn’t it possible in WordPress core any longer?

    Report

    • Sarah Gooding

      It’s a change that Facebook is making to its API, requiring authentication in order to display embeds.

      Report

      • Michael

        Yes, I do fully agree with that.

        But how does that justify putting the feature into JetPack instead of core? If it can be done in JetPack, surely it can also be done in core too and keep that functionality in core as it was instead of farming it out to a separate plugin.

        Report

        • Sarah Gooding

          Because it’s more plugin territory since it now requires users to register as a Facebook developer and create an app to get API credentials. Jetpack is going to do that on behalf of users so they don’t have to mess with any of that to keep their embeds working.

          Report

  2. Franco Heldt

    Please add GDPR notice and acceptance button vor visitors before including any external embeds and/or scripts. Otherwise this feature is pretty useless for euopean countires.

    Report

    • Jeremy

      Those embeds are still part of WordPress itself today, alongside many other embed providers. You can find the full list here.

      If you would like to use one of those embed options on your own site (whether they’re provided by WordPress itself or by a plugin like Jetpack), but you would prefer for your site visitors to have to give their consent before the embed content is loaded, you will need to use a plugin.

      While I do not have personal experience with it, I’ve read good reviews about this plugin to manage such restrictions on your site.

      Report

Comments are closed.

%d bloggers like this: