Jetpack

Spring Has Sprung; Jetpack 2.2.3

Hello Jetpack community,

We’ve been hard at work on Jetpack over the last couple of weeks. Since releasing version 2.2.2 (which was mainly a bug fix release), we have focused our attention on making sure that Jetpack will play nicely with WordPress 3.6 when it is released. Here are the highlights:

  • Yahoo! Updates API is going away, so Yahoo! has been pulled out of Publicize;
  • The Shortcode module now includes a Bandcamp shortcode;
  • The Audio flash player was removed in 2.2.2 for security reasons. We fixed the vulnerability and reenabled the flash player;
  • The plugin adds Infinite Scroll support to Twenty Thirteen;
  • With Jetpack 2.2.3, the reply-title portion of the comment form can be styled by the theme;
  • and many other things that you can read about in the changelog.

Keep an eye on our news feed! We will be posting some articles on how to use Jetpack-beyond-the-basics, plus some on “getting to know”-the-Jetpack-folks.

Thanks, as always, for following along with us. Here are some updated ways to get in touch:

This entry was posted in Uncategorized. Bookmark the permalink.

22 Responses to Spring Has Sprung; Jetpack 2.2.3

  1. sushubh says:

    Any plans to bring WordPress.com 2FA to WordPress.org through Jetpack? It might be complicated but would massively improve the security of the blogs.

    • Tim Moore says:

      The version we have on WordPress.com is specific to our service; moving it to Jetpack would require forking what we have. Definitely something we are looking into, though :)

      • sushubh says:

        Right. I thought about a scenario where I could login to any connected WordPress.org blog with my WordPress.com account. But I guess there are lots of possible issues with this type of implementation. Anyways… Recent updates have been very cool. I love the addition of Pocket share button for example.

        Would like some options for automated position change of the sharing buttons. An option to place them above the content maybe?

      • Tim Moore says:

        For moving sharing buttons, give this a try:
        a. use the sharing_display( '', true ); as a Template Tag. Place it in your theme where you want the sharing buttons to appear.
        b. in your theme functions.php, place remove_filter( 'the_content', 'sharing_display', 19 ); and remove_filter( 'the_excerpt', 'sharing_display', 19 );

        On logging in, that is also something we are looking at. Maybe sometime this summer :)

  2. Jetpack suggestions…

    1) Customizing Sharing icon placement. Right now, they’re only displayed at the bottom of a post. It’d be nice to display it under the headline as option or even vertically next to a post (as I currently achieve via Digg Digg).

    2) Mobile Theme widgets. Let me remove dekstop widgets and add widgets with mobile-specific code instead of forcing me to update the plugin code after every update.

    3) Import Feedburner email subscribers into Subscriptions and somewhat related provide a method to migrate Feedburner feed to WordPress/Jetpack as I assume Google will be killing it sometime this year.

    4) Allow Publicize to push to Facebook Pages, versus individual Facebook account.

    Thanks for considering these and if they already exist, I humbly apologize! :)

    • Tim Moore says:

      1) You can achieve this by doing the following:
      a. use the sharing_display( '', true ); as a Template Tag. Place it in your theme where you want the sharing buttons to appear.
      b. in your theme functions.php, place remove_filter( 'the_content', 'sharing_display', 19 ); and remove_filter( 'the_excerpt', 'sharing_display', 19 );

      2) I’ll investigate this further.

      3) Importing subscribers to our Subscriptions service has been a long requested feature. Our concern, and the thing we are investigating before releasing an importer, is that this could be easily used to spam email addresses. We’ll keep you up to date on what we come up with, though please bear with us as it may take some time.

      4) Publicize is already capable of this :)

      Thanks for the feedback, it is much appreciated.

      • Thanks for the guidance and info! FYI I suppose the email stuff could be abused. But I could just as easily take the addresses from WordPress and the addresses from Feedburner and populate something like a MailChimp list. So the potential for abuse always exists. Obviously you guys dont’ want to be the vector, which I can understand. I wonder if there’s a way to authenticate to Google and grab them programmatically? And I am concerned with what’s going to happen to all my Feedburner subscribers once Google kills it… I hope someone, somewhere (WordPress or otherwise) is working on a strategy to move them. Thanks!

      • Tim Moore says:

        Google has shuttered the Feedburner API, so there is not currently a way for us to directly access your subscriber logs (part of what makes this an issue). We do need to find a way to mitigate abuse, as much as we can. Otherwise our servers will get blacklisted by email providers, which is not something that we want to have happen given our volume.

      • Can I use the same trick for the placement of the Like buttons?

      • Tim Moore says:

        No, the same code won’t move the Like button. I’m looking into how to move the Like button and will update you soon.

  3. Any news on providing support for custom post types, custom taxonomies and custom fields?

  4. paradox says:

    plugin changelog mentions the long-awaited JSONAPI support for custom post types and metadata! (yet not mentioned anywhere here…)

    Any documentation updates for this?

  5. I’m really looking forward to when I can connect more than one Twitter account to Publicize. That’s something I’ve long been wanting.

  6. Is there a way to either import Feedburner email subscribers to Jetpack, or to enter them manually? Thank you!

    • Tim Moore says:

      No, there is not currently an import feature.

      • Okay, thanks! Is there a way that I could manually type all of my current subscribers into Jetpack so that they would not have to resubscribe?

      • Jeremy says:

        Jetpack doesn’t allow you to import subscribers from a third-party service at the moment.

        To make it easy for your existing subscribers to subscribe again using Jetpack Subscriptions, I would suggest the following:

        1. Create a new Page on your site, named “Subscribe”
        2. Insert the following shortcode in the page content:

          [jetpack_subscription_form]

        3. Send a link to that page to all your subscribers, to allow them to subscribe using Jetpack Subscriptions.
Follow

Get every new post delivered to your Inbox.

Join 61,642 other followers