Checked in at The Porter Portland, Curio Collection by Hilton.
#Jetpack GM
Checked in at The Porter Portland, Curio Collection by Hilton.
#Jetpack GM
Checked in at Thai House Restaurant.
#jetpack meetup with the local @wordpress crew
I’ve just released version 1.8 of both Keyring, and the Keyring Social Importers. This version includes a new service file, and an accompanying importer, which allows you to import content from a Jetpack-powered WordPress site, using the WordPress.com REST API. That means any site hosted on WordPress.com, or any self-hosted site with the Jetpack plugin installed. There are also a few key fixes for the Twitter and LinkedIn services/importers, so it’s a nice update.
The new importer will pull across the entire content of posts, including tags. Similar to the Instapaper importer, it attempts to avoid duplicate content issues by marking pages as noindex
if they come from imported content.
This is another piece of the puzzle required for me to create a complete archive of my digital footprints over on Dented Reality, now that I’m blogging here. This post should be imported over there automatically within an hour.
Note that currently the importer doesn’t sideload any media items (will add that soon) or support geo data (again, I’ll add that when I get a chance).
Check it out, and please use responsibly!
Checked in at National Mechanics.
Lunch with #jetpack #vaultpress crew.
Checked in at Fajita Grill.
#burritofriday with (most of) the #Jetpack crew
As a developer, I’m a huge fan of “red changesets”; when you get to delete more code than you add. Less code means less maintenance, less potential for bugs, security problems, etc. Today I got to “red changeset” the plugins powering this website because I realized I could just go ahead and delete the plugin I was using for update notifications.
I’ve been running a plugin here for a while now that emails me when I have updates available for plugins, themes or core on my WordPress installation. With the latest version of Jetpack though, I get that notification via a simple little indicator on WordPress.com (and I’m there every day already). In addition to the notification, I’ve enabled the auto-update feature for all plugins on all sites connected via Jetpack, so now I don’t even have to think about keeping my plugins up to date.
There’s a lot more cool stuff coming in this Jetpack/WordPress.com integration, and I’m really excited to see (and work on) what we can do to help make life easier for self-hosted users while leveraging the power of WordPress.com.
Last night, I preemptively tweeted about the upcoming release of Jetpack 2.0:
I can't wait for the very-near release of @jetpack 2.0. It is loaded with awesomeness and magic.
— Beau (@beaulebens) November 7, 2012
I’m working on a new WordPress theme (for this site, and it’ll be released for download once complete). The theme is deeply integrated with Jetpack, and one of the things I wanted to do was have the Jetpack Sharing buttons appear in a location other than the very end of the content. Normally they are applied as a filter on the_content, so they just appear right at the end. I wanted to relocate them into a different location, and it turns out that’s really easy to do with the power of jQuery.
jQuery( document ).ready( function( $ ) { // Relocate Jetpack sharing buttons down into the comments form jQuery( '#sharing' ).html( jQuery( '.sharedaddy' ).detach() ); } );
The #sharing
selector is just the DOM location where I want to move the buttons to, and the .sharedaddy
one is the container that Jetpack places its buttons in normally. We just detach it from the normal position and then dump it into the new location exactly as it was.