Jetpack 6.6 Improves Site Verification Tools, Asset CDN Module Now in Beta, Gutenberg Blocks Coming Soon

Jetpack 6.6 was released today with an update to the Site Verification tools that enables one-click verification and sitemap.xml registration with Google.

This release also introduces the beta of Jetpack’s Asset CDN. The new module, built on the same infrastructure as the Photon CDN, speeds up sites by cloud-hosting widely-used Jetpack and core WordPress scripts, styles, and assets. It takes a load off of users’ servers and increases the allowed maximum concurrent connections through Photon. Once it is ready for use in production, the Asset CDN will be a new opt-in feature that can help speed up Jetpack’s 5+ million active installations.

Version 6.6 also adds the necessary infrastructure for new Gutenberg blocks. The activity on the plugin’s GitHub repository indicates the team is working on a number of blocks for existing features, including things like recipes, shortcodes, Jetpack subscription form, Simple Payments, Publicize, the contact form, tweet shortcode, VR shortcode, Giphy, and more. Everything touching the editor is in the process of being ported to blocks. Many of the blocks are already complete and some are still in progress. Some features, such as support for tiled gallery layouts, have bugs that need to be sorted before Jetpack will be ready for WordPress 5.0.

Jetpack 6.6.1 will be going out soon to address a bug with social icons that this release introduced. In the meantime, users can paste the CSS in this gist into Appearance > Customize > Additional CSS to provide a temporary fix.

8 Comments


  1. Thanks so much for the CSS which provides a temporary fix for the bug with social icons in Jetpack 6.6 — exactly what I was looking for!

    Report


  2. Just updated my Jetpack to 6.6. I haven’t tried out their Assest CDN but definitely willing to give it a try. Thanks for sharing the update.

    Report


  3. I love the idea of assets CDN. It’s brilliant. Thanks for making it available for free!

    Report


      1. GDPR requires information to and consent of user before any request to CDN.

        Most CDN providers seem to disagree with your approach today: you can check CloudFlare or KeyCDN‘s documentation about this for example. Those companies offer Data Processing Agreements to help you as a site owner remain compliant.

        Automattic also offers Data Processing Agreements; you can request one by following the instructions here.

        It’s also worth noting that WordPress itself loads data from a CDN by default. This would make 30% of the web non-compliant with the GDPR if your statement above were true. This is discussed here:
        https://core.trac.wordpress.org/ticket/44001

        The ticket is still open. Don’t hesitate to chime in with your remarks if you’d like.

        Most Jetpack functions void GDPR, using Jetpack in EU is high legal risk.

        Jetpack was updated before the GDPR came into effect, and a few things were added to allow you to keep using the plugin and make sure your site remains compliant with the GDPR. You can read more about this here. Note that just like with every other plugin, there is no simple turn-key solution: you do need to take action on your site (like updating your privacy policy) when installing additional plugins that can deal with personal information on your site.
        You can also check Jetpack Privacy Center to learn more about all this and find links to the documents you may need.

        Report


  4. GDPR requires information to and consent of user before any request to CDN.

    Most CDN providers seem to disagree with your approach today: you can check CloudFlare or KeyCDN‘s documentation about this for example. Those companies offer Data Processing Agreements to help you as a site owner remain compliant.

    Automattic also offers Data Processing Agreements; you can request one by following the instructions here.

    It’s also worth noting that WordPress itself loads data from a CDN by default. This would make 30% of the web non-compliant with the GDPR if your statement above were true. This is discussed here:
    https://core.trac.wordpress.org/ticket/44001

    The ticket is still open. Don’t hesitate to chime in with your remarks if you’d like.

    Most Jetpack functions void GDPR, using Jetpack in EU is high legal risk.

    Jetpack was updated before the GDPR came into effect, and a few things were added to allow you to keep using the plugin and make sure your site remains compliant with the GDPR. You can read more about this here. Note that just like with every other plugin, there is no simple turn-key solution: you do need to take action on your site (like updating your privacy policy) when installing additional plugins that can deal with personal information on your site.
    You can also check Jetpack Privacy Center to learn more about all this and find links to the documents you may need.

    Report


    1. @Jeremy: Whataboutism won’t help. Jetpack out if the box is not GDPR compliant, period.

      There is no notification during installation that a) a data processing agreement is required and b) where it would be available and c) that it is mandatory.

      WordPress core does not use CDN by default, emojiscript is only included in very old subset of browsers, oembed is only used if embeds are published actively by user, which requires GDPR notifications and other data processing agreements anyway.

      Instead of censoring these impotant hints, better do some interviews with leading EU GDPR lawyers and publish the results.

      Report


      1. There is no notification during installation that a) a data processing agreement is required and b) where it would be available and c) that it is mandatory.

        We indeed do not display such notification on installation. We do, however, display information when you want to connect your site to WordPress.com: to do so you must agree to our Terms of Service and we inform you about the data that is shared with our service when connecting with WordPress.com. What you do from there is up to you, and will depend on your site, your readership, the features you use on that site, and the GDPR recommendations you may have received from an attorney in your country. We cannot give specific legal advice about your particular site of course, because we are not your attorney.

        Instead of censoring these impotant hints, better do some interviews with leading EU GDPR lawyers and publish the results.

        We published the results of our GDPR work in this blog post a few months ago.

        If your attorney disagrees with our approach, it’s indeed best if you do not use Jetpack on your site.

        Report

Comments are closed.