Thanks for contributing to Edit Flow v0.7-beta1. This release was tagged on Friday, December 23rd and we’d love to release the new 0.7 version by the end of this week (Dec. 30th). If you’d like to help out, we’d love constructive feedback in the forms of testing, documentation, code, or translations. Bug fixes will be prioritized, and big features will be queued for a future release.
For a sense of what Edit Flow offers as of v0.6.5, please check out the readme, changelog, and install it in your production or local environment if you haven’t already. In a nutshell, you have custom post statuses, editorial metadata, email notifications, a calendar and a story budget, and editorial comments. In v0.7, you have all of that plus the following improvements:
- Entire plugin was rewritten into a modular architecture (e.g. each feature is broken into a module you can enable or disable). The point of the modular architecture is to make it much easier for others to contribute new features. For the end user, there’s a brand new settings page where you can manage your modules. Each module then registers a configuration view for module settings. Most have options to choose which post types you’d like it activated for, along with other configuration options.
- Calendar is far more functional. Content is viewed in a six week view by default, and number of weeks is configurable in screen options. Posts can be dragged and dropped between dates. Click on a post title to get the details about the post, including editorial metadata.
- Custom statuses can be drag and drop ordered with AJAX. All statuses (including core ‘draft’ and ‘pending’) can be edited or deleted.
- Editorial Metadata terms can be ordered with AJAX. Terms can be made “viewable” and then will be displayed on the manage posts view and calendar if enabled.
- Story Budget shows “viewable” editorial metadata and fixes a few bugs, including not showing posts in a subcategory of a parent category.
- Notifications/subscriptions are filtered so you can disable the auto-subscribing of authors or editorial commenters.
As far as testing goes, everything in beta1 should work as did in v0.6.5. Use v0.7-beta1 as you would normally, and let us know if you run into any issues. Also, if you have a working version of v0.6.5 with a fair amount of data, please backup your database and try the upgrade path to v0.7-beta1.
If you’d like to contribute code, we have a few small stories still open:
- Clean up the print stylesheet for the story budget (#20946763) – Simple CSS changes to the print stylesheet
- Users should be able to select text within the calendar overlay without dragging it (#21134995) – If you click on the post title for a post that’s draggable, you should be able to select text from the overlay. Currently, it instantiates the sortable code
- CSS3 columns on Editorial Metadata when the metabox appears under the post editor (#20646467 – Simple CSS again from this previous conversation
Simply fork us on Github and submit a pull request.
If you’d like to help with documentation, I’ll write a post about what needs to be done shortly.
Language translations are always welcome too.
Edit Flow v0.7-beta1 is available for download on Github. Feel free to report bugs, feedback, etc. in the comments for this post and I’ll create Pivotal stories from there. Thanks again for your help.
