Once again we've made some changes to ensure that Jetpack plays well with the AMP plugin. To test, try the following:
- Install the AMP plugin.
- Switch AMP mode (AMP > General) to
PairedorClassic. - Activate the Carousel module, the sharing module, and ensure that
SCRIPT_DEBUGis set tofalseon your install. - Create a post with a gallery
- Add a Facebook sharing button to that post.
- Share that post on Facebook once.
- Comment on one of the images in the gallery.
- Load the post in a non-AMP view, and in the 3 modes available in the AMP options screen: Native, Paired, Classic. (
Nativemode - all views are AMP views;Pairedmode - add?ampto get to the AMP view;Classicmode - add/ampto get to the AMP view)- In non-AMP views: Does the Carousel modal work? Do you see the comment in the Carousel modal? Do you see the sharing buttons? Do you see the counter next to the sharing button? Do you see the
jetpack.cssfile when viewing source? - In AMP views: you should not see the Carousel. You should see a special styling of the sharing buttons. If you check the network tab in your browser tools, you should see a request to pixel.wp.com when logged out. You should not see a
jetpack.cssfile in the source.
- In non-AMP views: Does the Carousel modal work? Do you see the comment in the Carousel modal? Do you see the sharing buttons? Do you see the counter next to the sharing button? Do you see the
In all cases:
- You should not see any js errors in the browser console.
- You should not get any PHP notices in your debug log.
Now try adding the following to a functionality plugin on your site:
add_filter( 'jetpack_implode_frontend_css', '__return_false' );
add_filter( 'jetpack_sharing_counts', '__return_false' );Once you've done so, check the non-AMP view again:
- you should not see the sharing counter on the Facebook button.
- you should not see the
jetpack.cssfile in your source.
This release adds one more block to the list of blocks available in Jetpack. The Gif block will allow you to quickly search and add images to your posts. To test it, load the block editor and search for the new Gif block. You should then be able to search for images using any keyword, choose an image, and add a caption if you want to. The image should be displayed nicely on the front end of your site.
This release introduces a brand new feature, "Copy Post". The feature is not activated by default, so you'll need to go Jetpack > Settings, search for the feature, and activate it. Once you've done so, here is how you can test the feature:
- Create a test post that has the following: title, content, except, featured image, post format, categories, and tags (be sure the theme supports Post Formats, like Twenty Seventeen; Twenty Nineteen does not).
- From
/wp-admin/edit.php, hover over the test post and then click Copy. - Verify the draft post that loads contains all of the data from the existing post.
- Publish, and verify all information was saved without errors.
- Repeat the same with pages and a custom post type.
As you may know, Google+ will be shut down in April 2019. Google reported that intermittent service failures may begin as soon as January 28. We've consequently opted to deprecate the Google+ features of Jetpack in this release. 4 different features are impacted by the changes:
If you go to Settings > Sharing in your dashboard, or try to publish a new post on a site you had previously connected to Google+, you will now see a notice in the Publicize settings, to let you know about the upcoming change. In Settings > Sharing, you should not be able to create a new connection anymore.
The Google+ sharing button will not be displayed on Jetpack sites anymore.
- If you had not added a Google+ button to your site before, you won't see the option to add one to your site anymore. Under Settings > Sharing, you will not see any Google+ option.
- If you had added a Google+ button to your site in the past, you will see a new button instead, when you are logged in to your admin account. That button will invite you to remove that deprecated service from your site. Your readers, however, won't see anything.
Jetpack used to offer a Google+ embed solution. We now only display a link to the Google+ post instead, for posterity. To test this, you can try adding the following to a post on your site:
- Add
https://plus.google.com/106672383817838331060/posts/ddyLLrp2mw7on its own line. - Add a
[googleplus url=https://plus.google.com/106672383817838331060/posts/ddyLLrp2mw7]shortcode on its own line. - Preview the post. You should see two clickable URLs each in their own paragraph tag.
Jetpack also offered a Google+ Badge widget. If you used such a widget on your site, we will remove it from your sidebar for you. To test this, try the following:
- On the stable version of Jetpack, add a Google+ Widget to your sidebar. You can use
https://plus.google.com/+JeremyHerveas a "Person" URL, orhttps://plus.google.com/communities/101504763068635549461as a "Community" URL. The widgets should work just fine. - Update to the Beta version; the widgets should be gone.
At any point during your testing, remember to check your browser's JavaScript console and see if there are any errors reported by Jetpack there.
Thank you for all your help!