v0.7.5: Enhancements and bugfixes

A couple of localizations, some small enhancements, and another laundry bag of fixes:

  • 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.

v0.7.4: Enhancements and bugfixes

Some small enhancements, and a laundry bag of fixes:

  • 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.

v0.7.2: Custom statuses for contributors

Thanks to an awesome contribution from Daniel Chesterton, we have an oft-requested feature to give you today: custom statuses for contributors. Previously, your contributors and other users without the ‘publish_posts’ capability had two options, “Save as Draft” or “Submit for Review”. With Edit Flow v0.7.2, they can save content to any stage of your workflow.

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.

Edit Flow v0.7.1: Enhancements and bugfixes

Coming to you live from a rainy Portland afternoon: Edit Flow v0.7.1. This is mostly a enhancements and bugfixes release with the following points of interest:

  • 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.

Edit Flow v0.6.5: Fixes post timestamp issue when using custom statuses

Out just a moment ago, Edit Flow v0.6.5 has one purpose: to fix an issue with the post timestamp being set when you set a post to a custom status.

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.

Edit Flow v0.6.4: Bulk edit custom statuses and bug fixes

Late on the release blog post for this one, sorry. A week or so ago, we finished Edit Flow v0.6.4, which you can now download from the WordPress.org forums.

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.

Edit Flow v0.6.3: Email bug fix and seeing unpublished content

We released Edit Flow v0.6.3 on Monday to fix/add a few things. First, we restored email notifications to old delivery method instead of queueing with WP cron because of reliability issues. This should fix any and all notification delivery problems. Second, per a request in the forums, we’ve added the ability to see just “unpublished” content on the story budget and editorial calendar. This could be pretty useful for those newsrooms with a lot of content published on a daily basis.

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

Edit Flow v0.6.1: Custom post type support and minor improvements

We released Edit Flow v0.6.1 yesterday. While the version number suggests a minor upgrade, we’ve put a lot of work into this release and have a number of new features, improvements and fixes that you’ll enjoy.

Note: Edit Flow v0.6 and above requires WordPress 3.0

Custom Post Type Support

Edit Flow now supports Custom Post Types

Edit Flow now supports Custom Post Types

It’s a feature many of you have been asking for since Custom Post Types were added in WordPress 3.0. We’re happy to announce that Edit Flow is now custom post type-friendly. You can easily add or remove any Edit Flow feature to your custom post types with a few lines of code. We’ve included some code samples to get you started.

Note: Custom post statuses are now enabled for pages by default as we’ve removed the option from the settings. You can disable them if you’d like with the remove_post_type_support() method.

i18n (Internationalization)

We’ve heard many of our users across the world are interested in translating Edit Flow into their native languages. With this release, we’ve gone through and cleaned up the plugin to make that easy. If you’re interested in providing a translation for Edit Flow, please get in touch and we’ll gladly include it with the plugin. Pig latin is a language too!

Filtering Users and Usergroups

User and Usergroup search and filters

User and Usergroup search and filters

If you have a large list of users, you now how difficult it can be to scroll through and find the exact person you’re looking for. We’ve added filters and search-as-you-type to user and usergroup lists to make that a little easier.

Email Queueing

Emails sent by Edit Flow are now optimized to use queueing for improved performance (and to avoid being flagged as spam).

Bug Fixes

We’ve also fixed a number of bugs:

  • Users without JavaScript no longer see the status dropdown
  • Users with JavaScript no longer see the respond button for editorial comments
  • Contributors should not have the ability to publish through Quick Edit
  • Proper i18n support (Thanks Beto Frega and others)
  • Editorial Comments issue in IE (Thanks asecondwill and James Skaggs)
  • Always email admin feature was not working (Thanks nicomollet)
  • Notifications for scheduled posts did not include links (Thanks erikajurney)

For the full list of changes in this release, view the changelog. If you run into issues, the best place to go for help is the WordPress.org Support Forum.