• New Japanese localization thanks to naokomc.
• New French localization thanks to boris-hocde.
• Allow custom post statuses to be completely disabled for a post type, preventing situations where ‘draft’ posts could disappear when the draft status was deleted.
• Better implementation of the hack we have to employ for editable slugs in the post edit screen. Thanks cojennin for the assist.
• Editorial metadata names can now be up to 200 characters (instead of 20 previously). Props cojennin.
• Bug fix: Load modules on ‘init’ so the strings associated with each class can be properly translated.
• Bug fix: Pagination functional again when filtering to a post type.
• Bug fix: Pre-PHP 5.2.9 array_unique() compatibility.
• Bug fix: Respect the timezone when indicating which day is Today.
• Bug fix: Calendar should work for all post types, regardless of which are supposed to be added to it.

See Github for all of the closed issues.

Also of note: edit(orial) flow is coming to core for WordPress 3.6! This will mostly be bug fixes around custom statuses, but I’m hoping to release Edit Flow v0.8 around the same time. Let me know if you’d like to help with contributing.

As always, please hit us with questions, feature requests, and bug reports in the WordPress.org forums.

• Added ‘Scheduled’ as one of the statuses you see in the ‘Posts At A Glance’ widget. ‘Private’ and other core statuses can be added with a filter.
•  Sort posts on the Manage Posts view by visible editorial metadata date fields.
• Modify email notifications with two filters.
• Bug fix: Proper support for unicode characters in custom status and editorial metadata descriptions.
• Bug fix: Show the proper last modified value on the story budget when the server’s timezone is not set to GMT. Props danls.
• Bug fix: Make the jQuery UI theme for Edit Flow more specific so it doesn’t conflict with core modals.
• Bug fix: Use the proper singlular label for a post type when generating notification text.
• Bug fix: Post slug now updates when the post has a custom status.
• Bug fix: When determining whether a user can change a post’s status, check the ‘edit_posts’ cap for the post type.

See Github for all of the closed issues.

As always, please hit us with questions, feature requests, and bug reports in the WordPress.org forums. If you’d like to help out, check out our guide to contributing.

Here’s what the submit meta box now looks like for your contributors:

You can use a simple filter to restrict your contributors to only changing specific statuses. If you did so, it would look like this:

In this release, we’ve also incorporated the following changes:

• Support for trashing posts from the calendar. Thanks Dan York for the idea and a bit of code.
• Updated codebase to use PHP5-style OOP references.
• Fixed some script and stylesheet references that had a double ‘//’ in the URI path
• New edit_flow_supported_module_post_types_args filter allows you to enable custom statuses and other modules for private post types

See Github for all of the closed issues.

As always, please hit us with questions, feature requests, and bug reports in the WordPress.org forums. If you’d like to help out, check out our guide to contributing.

• Shows the year on the calendar and story budget if it’s not the current year.
• Allows users to save post subscriptions the first time they save the post. This also fixes the bug where a user wouldn’t be subscribed until they saved the post twice.
• Changed the behavior of notifications for the user changing a status or leaving a comment. Previously, they’d receive an email with the action they just performed; now they do not. This can be changed with a filter.
• New Italian localization thanks to Luca Patané.
• Bug fix: Auto-subscribe the post author to their posts by default but make it filterable.
• Bug fix: Only show “authors”, or contributors and above, in the user dropdown for the calendar and the story budget. This new behavior can be filtered out however.
• Bug fix: Metaboxes are registered with proper priority. Props benbalter
• Bug fix: If a user hasn’t ever opened the calendar before, the date should default to today, not the Unix Epoch
• Bug fix: Prevent editorial metadata filters from stomping on others’ uses by actually returning the original value when we don’t want to manipulate it
• Bug fix: Specify a max-width on <select> dropdowns in the calendar and story budget so long values don’t break formatting

See Github for all of the closed issues.

On that note, getting involved with the code side of the project is now easier than ever. We’ve moved all of our project management to Github.

One way to get acquainted with the code base is by producing a functional code snippet. We have a list of code snippets requested at one point or another, including:

• Remove the publish capability for certain statuses so you don’t accidentally publish a pitch or similar pre-production post (#55)
• Send out reminders to users based on the value in an editorial metadata date field (#48)
• Include users listed in the “User” editorial metadata field as recipients of notifications (#46)

If your code snippet works well and meets our standards, we’ll add it to our site documentation and thank you profusely.

Modular architecture

The biggest change in Edit Flow v0.7 is that the entire plugin has been rewritten into a modular architecture. Each feature is a module you can enable or disable. Most modules have a configuration view where, among other things, you can change which post types you want to apply the feature to. No more dealing with code snippets for adding custom statuses to your custom post type. There are also standard UIs for customizing each feature.

One purpose of the modular architecture is to make it much easier for others to contribute new features. It’s super easy to plug a new module into our framework and have it work with existing features. Learn more about contributing code.

Month-by-month calendar with AJAX drag and drop

The calendar now defaults to showing the upcoming six weeks, and you can change this range to a week or up to twelve weeks. Unpublished posts can be dragged from date to date so you can keep track of what’s going to be published when. Click on a post title to see all of the details about the post (including your viewable editorial metadata).

Other improvements

Along with the big changes, we added a lot of polish to each feature, including:

• Editorial metadata can appear in the calendar, story budget, or manage posts screen by marking a term as “viewable”.
• Editorial metadata display in nicely formatted columns if you move its post meta box under the editor.
• Prioritize your custom statuses and editorial metadata with drag-and-drop. You now have full control over what appears in what order. This also affects presentation of this data in the calendar and elsewhere.
• “Draft” and “Pending Review” post statuses can be deleted.
• Notifications have a filter so you can disable auto-subscribing the post author or users who edit the post.
• Fixed the order of execution for saving notifications, so you can auto-subscribe user groups based on post status using a code snippet.
• Improved how the story budget date range works — now you’ll pick a start date and number of days to show.
• Switched to jQuery Datepicker, which has a much friendlier UI, for all date selection.

Credits for this release

Edit Flow is an open source project, and we’re indebted to many people for helping us improve the code and experience. In particular, we’d like to mention:

• Ben Balter, Nick Hamze, and Rinat Khaziev for their code contributions and testing.
• Andrew Witherspoon, Andrew Spittle, Lauren Rabaino, and Chelsea Otakan for their design expertise.
• Steve McConnell for extensive testing and usability feedback.
• The Noun Project for an awesome set of free to use icons.
• Automattic for allowing me (Daniel) to work on Edit Flow as a 20%, sometimes 50-80%, project.

Try out Edit Flow v0.7 and let us know what you think. Want to help make the next version even better? Check out our introduction to contributing, and get involved!

The coolest thing about the WordPress community, is that well, it’s a community. Developers don’t just write code in vacuum and send it on its way, but rather are part of an ecosystem of mutual inspiration and informal collaboration.

WP Document Revisions a document management and collaboration plugin for WordPress announced recently that the latest release will automatically detect Edit Flow, if installed, and will pull Edit Flow’s workflow tools into its own interface — cool, huh?

While this is undoubtedly a great pat on the back for Edit Flow and its efforts, the bigger news for the community is that now teams can use Edit Flow’s proven workflow tools in their newsroom with virtually any file format — Word, Adobe, images, anything.

If you want to give it a try, simply download and activate WP Document Revisions and begin working, no additional configuration required if you’ve already got Edit Flow installed.

Basically, if you set a post or a page to a custom post status, the publication timestamp would be set and saved. Upon publication of the piece, the publication date was set to whenever you originally saved the post with a custom post status. Our fix works around some of the limitations of WordPress core on this issue.

WordPress.org user saomay deserves our thanks for their patience in helping track down the issue, and testing the fixes. It was originally reported in the forum.

It’s worth noting that we’re actively working on v0.7. You can follow our discussion on our development blog. We’ll be looking for beta testers, translators, and documentation writers shortly. If you’d like to help out, let us know in the comments.

The most significant improvement is that you can properly bulk edit posts and pages with custom statuses.

For editorial metadata, we’ve added a “Number” metadata type, along with a link to easily clear the field when dealing with date metadata.

Lastly, we’ve added filters for the “Posts I’m Following” widget on the dashboard, and for the posts that appear in the calendar. If you’ve wanted to add custom post types to either of these interfaces, now’s your chance!

Check out our full changes in the changelog. Also, we’ll be moving from our Google Group to a development P2 if you’d like to follow along.

As always, please hit us with feedback, ideas, and questions in the WordPress.org forum.

To increase (or decrease) the number of posts from the default of 10, just add a small code snippet to the functions.php file in your theme. For instance, the following would increase the number of stories shown per category to 20:

add_filter( 'ef_story_budget_query_limit', create_function( '', 'return 20;' ) );

Of course you could split out the create_function call above to actually use a function that you’ve defined elsewhere in your functions.php file, but unless you’re going to have complicated logic to decide how many posts to display, I don’t see the need for anything beyond that one-liner.

Any further tutorials you would like to see on our blog here? There are lots and lots of filters baked into Edit Flow that are just dying to be unlocked by you, our users—let us know in the comments below what you’d like to customize or see in action and we’ll do our best to explain how to use it! And as always, for support questions, please post your question here.