Co-Authors Plus 3.1: Manage co-authors from Quick Edit, misc improvements

Co-Authors Plus makes it possible to assign multiple bylines to posts, pages, and custom post types via a search-as-you-type meta box. Thanks to Mike Patek at Vocativ, version 3.1 includes co-author management via Quick Edit:

2014-03-17 at 3.48 PM

Also in this release:

  • Updated Spanish translation, courtesy of sergiomajluf.
  • Now matches core behavior when displaying author archive on multisite: user of the blog, or previously published author on the blog.
  • Breaking change: “Create Profile” link is no longer shown by default on the Manage Users screen. Instead, it can be enabled with the coauthors_show_create_profile_user_link filter.
  • Guest authors work properly with Jetpack Open Graph tags. Props hibernation.
  • Guest author profile editor now supports a few different fields. Props alpha1.
  • New coauthors_count_published_post_types filter for specifying the post type(s) used when calculating the user’s number of published posts.
  • Bug fix: Ensure post_author is set to one of the co-authors assigned to a post.
  • Bug fix: Filter author feed link for guest authors on the author page. Props hibernation.
  • Packages a composer.json file for those using Composer.
  • Beginnings of unit test coverage for core features. Increased minimum required WordPress version to 3.7 because unit testing framework doesn’t work reliabilty below that.

Please leave feedback, bug reports, and praise in the forums. You can also get involved with development on Github.

Moving on up

If you’re reading this post, then you’re seeing a brand new hosted by Digital Ocean. I’ve been a long-time WebFaction user, but the allure of cheap SSD was too much to pass up.  That, lack of two-factor auth support, and generally feeling like WebFaction is stuck in the early 2000′s caused me to branch out.

And I’ve been incredibly impressed. The machine is fast (although I guess I’m jinxing myself now), the control panel is just what I want it to be, and the price make me feel like I’m committing a robbery.

For anyone that wants to take a peek at what I’ve done, the repo is in Github. It was intended to be a one-day project, but I ran into some domain-mapping hell. As it turns out, core doesn’t fully support domain mapping as I thought it did.

Lastly, I provisioned my new machine using masterless Salty WordPress (work in progress). Hoping to align incentives such that Salty WordPress continues to be the best way to provision local and production WordPress machines.

What’s next: Digital First Media

Big news to break today: I’ve joined Digital First Media’s Thunderdome team as Senior Developer.

As some of you may be aware of, Digital First Media is the second-largest newspaper chain in the US. Under leadership from the likes of John Paton, Jim Brady, Steve Buttry, and others, DFM is investing heavily in digital, to the tune of $100 million annually over the next three years. Part of this investment is their “Project Unbolt“, and part is other, yet to be announced news products and infrastructure. WordPress will be a key component of the technology stack — and DFM’s Thunderdome team is the place where many experiments are happening.

Five and half years ago (wow how time flies), I wrote “One case against College Publisher” in which I outlined the importance of open source in publishing. Since then, I’ve worked in news largely from the vendor perspective — none of the newsroom opportunities I explored were the right fit. With Digital First Media, I feel like I’ve gotten my big chance at the big leagues. I look forward to helping DFM implement WordPress in a variety of contexts, as well as increasing my contributions to WordPress core, Edit Flow, WP-CLI, and other projects. Open source has a tremendous opportunity to impact news, and the news industry has a tremendous opportunity to contribute to open source.

Check out the announcement on Inside Thunderdome. If you want to join the fun, we’re hiring a frontend developer for my team.

#phppdx: WordPress as an Application Platform

Last night, I presented to ~25-30 people at the PDX PHP meetup on “WordPress as an Application Platform”. Even though I’m no longer with Human Made, I think what they’ve done with WP Remote (and Happytables) is the bleeding edge and worthy of sharing.

Ultimately, the point I wanted to get across is two-fold:

  • Many applications you could think of building are easily doable with WordPress.
  • WordPress-based products are even more interesting when you have a few, and durable components to share between them.

After the talk, I asked Zack for his feedback:

  • Went well: introduction via Freshbooks example really set the stage for what we were talking about. Avoided misunderstanding / different opinions of what a web application was.
  • Next time: Challenge people more. Explanation of how HM built WP Remote was a bit surface level. Could’ve gone deeper into the architecture as a frame of reference for people when they run into it.


All of the references I mentioned in the slides are available at the following links.

WP Remote components:

  • Job Agency - Asynchronous jobs system for WordPress, built on WP-CLI.
  • HM Rewrite – Wrapper for the WP Rewrite API.
  • h-api – Simple, descriptive API pattern. Needs work for public consumption.

Object cache drop-ins:

Future of WordPress: