Jetpack 3.2 Released, Introduces New Site Logo Feature for Theme Developers

Jetpack 3.2 was quietly released yesterday with a host of new enhancements for self-hosted WordPress sites. Following up on 3.1’s total re-branding of the plugin, 3.2 comes with speed improvements and better caching for related posts.

This release introduces the new ‘Site Logo’ feature that was added to themes in late July. The goal is to increase data portability across themes and standardize the way themes present logo upload.

The Site Logo feature has been added to Jetpack’s theme tools for any theme that opts to support it. It allows themes to optionally display the site’s title and tagline along with the logo and brings a new way for self-hosted WordPress sites to enjoy logo portability.

site-iconYou’ll also find a new Site Icon feature in this release, which lets you create an icon for your site that will be displayed as a favicon. If you don’t already have a favicon in place, this is an easy way to add one.

The previous release introduced the Portfolio Custom Post Type as the first of many planned custom content types. According to the changelog, Jetpack 3.2 adds a new Testimonials content type. In order to turn it on, one might expect to navigate to ‘Settings’ → ‘Writing’ → ‘Your Custom Content Types’, which is where the portfolio one is located. However, this feature is based on theme support and must be declared during after_setup_theme:

[php]add_theme_support( ‘jetpack-testimonial’ );[/php]

The Testimonials feature was actually added in a previous release, though not highly publicized.

Additional enhancements in Jetpack 3.2 include:

  • Improvements to API endpoints
  • oEmbed sources (Twitter, SoundCloud, Instagram, DailyMotion, Vine)
  • Indicators to make it easier to see which modules are active
  • Improved debug tool
  • Added “Remember Me” functionality to Single Sign On
  • Improved accessibility
  • Additional filters added for Widget Visibility

The release notes also include a few bug fixes, most notably the removal of the Google+ module. Since Google Authorship is now officially dead, Jetpack 3.2 sheds the dead weight of the authorship feature originally introduced in its 2.5 release.

The plugin description page on is sporting a new tagline. Previously, it read: “Supercharge your WordPress site with powerful features previously only available to users.”


The new tagline, “Your WordPress, Streamlined,” seems to reflect an interesting language change within that identifies sites as simply WordPress.

As of today, the Jetpack team has not yet officially announced the release on their blog, but the 3.2 update is available to users within the WordPress admin.


25 responses to “Jetpack 3.2 Released, Introduces New Site Logo Feature for Theme Developers”

  1. Hey Sarah, to enable the Testimonial post type, the theme needs to declare support for it.

    Adding the following to the functions.php file will enable the Testimonials post type:

    add_theme_support( ‘jetpack-testimonial’ );

  2. Thanks for this but I activated Site Icon and I’m a bit confused with related settings. When clicking on the module I get this highly explicit text: “Site Icon lets you create an icon for your site which is displayed as a favicon.” Great, but would someone just let me know WHERE and HOW this can be done? I simply didn’t find any related settings.

  3. I set my site icon some days ago and for a while it was working right, but now it shows a gmail site icon on the homepage and the correct one on my dashboard. So I tried removing it entirely so I could reset it, but that’s also not working properly. According to my settings, there is no current site icon, but still my dashboard shows the right one and the homepage shows the gmail icon. Someone please help me, I’ve searched everywhere else with no results. It seems I am the only one having this issue.

  4. I fixed it!

    Just curious.. does jetpack add a line of code to your theme if it detects that it may not have support for favicon?

    I am using a child “twentyfourteen” theme, so the support is definitely there. In the parent theme though, not the child of course But i found this little snippit of code in my child functions.php file that imported a favicon? It looks like jetpack may not be able to detect the support in the parent theme…

    Once I deleted the code it all worked, but curious nonetheless.


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: