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

25

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 WordPress.com 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:

add_theme_support( 'jetpack-testimonial' );

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 WordPress.org is sporting a new tagline. Previously, it read: “Supercharge your WordPress site with powerful features previously only available to WordPress.com users.”

jetpack-tagline

The new tagline, “Your WordPress, Streamlined,” seems to reflect an interesting language change within WordPress.com 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.

Would you like to write for WP Tavern? We are always accepting guest posts from the community and are looking for new contributors. Get in touch with us and let's discuss your ideas.

25 Comments


  1. I think most notable here is the new tagline and the language change. Curious to see how this is adopted (or not) throughout the WP community.

    Report


  2. I made a post (unanswered so far) on the plugin’s support page asking what oembed Twitter means since it was already built into WordPress.

    Report


  3. 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’ );

    Report


      1. Yea my bad, sorry. Would’ve sworn it wasn’t there when I wrote the comment :)

        Report


  4. 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.

    Report


    1. Once activated, it’s under Settings>General

      Report


      1. Yep, thanks! Not so obvious…

        Report


      1. It wouldn’t also hurt to include something more explicit in the module’s properties that currently only displays this sentence and lots of empty space below: Site Icon lets you create an icon for your site which is displayed as a favicon.

        Report


      2. mmm… site logo shows up on backend.. frontend im using twenty fourteen. with a child css to make it “proper” full width. Is there something i need to add to the theme so that the favicon shows up?

        Report


  5. I am glad they did this update. It now works with my multisite. Thanks Jetpack!

    Report


  6. Regarding the removal of dead weight, does that mean that Publicise via Google+ has been removed?

    Report


    1. No, Publicize via Google+ is still available. Only the Google+ Authorship module was removed.

      Report


  7. 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.

    Report


      2. Jetpack’s Site Icon is there on your site: http://i.wpne.ws/YV90

        However, I noticed that the Easy AdSense plugin adds code before the opening HTML tag in your source code. Could you check your plugin options, or any template tag you may have added to your theme’s header.php file, to make sure the plugin doesn’t add anything before the opening head tag?

        That might help with your favicon issue.

        Report


  8. 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.

    Report


    1. No, Jetpack doesn’t detect if you already use a favicon, either added by your theme or by a plugin. You’ll consequently need to check before you upload a Site Icon.

      Report


  9. I’m getting the following error when trying to add a Site Icon through Jetpack: Warning: unlink() [function.unlink]: No such file or directory in D:\Hosting\9778349\html\wp-content\plugins\jetpack\modules\site-icon\jetpack-site-icon.php on line 581

    Can you help?

    Report

Comments are closed.