Jetpack

Jetpack 2.0.1 Released

Today we released Jetpack 2.0.1 to correct various issues with Photon, Publicize, and Infinite Scroll. What did we fix?

Photon

  • Avoid distorting images that don’t have explicit width and height set, or that only have one dimension specified.
  • When images are linked to their full-size versions, also serve the full-size versions from the WordPress.com CDN.
  • If an image is already processed with Photon, don’t reprocess it.
  • Add support for the Lazy Load plugin.
  • Unbreak smilies. :)

Publicize

  • If a site has custom shortlink settings, use those rather than always using wp.me.
  • Disable the Publicize interface for any posts already publicized to reduce confusion.
  • Link to connected LinkedIn profiles on the connections screen.
  • Improve error handling.

Infinite Scroll

  • Child themes now support Infinite Scroll if the parent theme does.
  • Archives now properly load only posts that would be shown if Infinite Scroll wasn’t present.
  • Link to support documentation within the module when the active theme doesn’t support Infinite Scroll.

Those are the highlights, but we also fixed dozens of other issues reported by our users. For a complete list of changes, see the official Jetpack Changelog.

The update will be available in your WordPress dashboard shortly; alternatively, you can always download the latest version of Jetpack here at jetpack.me as well.

Remember to contact support or post in the support forum if you need help. These fixes are made possible by bug reports submitted by you and other users. Thanks for the help.

This entry was posted in Releases and tagged , , . Bookmark the permalink.

2 Responses to Jetpack 2.0.1 Released

  1. monkhousehosting says:

    Can in the next version be able to put in more then one contact form on a page?

    • Sheri says:

      There aren’t current plans to update the Jetpack Contact Form to allow more than one contact form per page, but we will consider working on that in the future. In general, putting more than one form per page might be confusing for visitors, and I would recommend using one per page anyway.

Follow

Get every new post delivered to your Inbox.

Join 63,480 other followers