1. Ruth Raventos

    Hello, as one of the co-founders of Nelio Software, I would like to comment that Edit Flow users might also consider installing our Nelio Content plugin.

    The free version includes a drag-and-drop editorial calendar, quality control, reference suggestions, publication analytics, and scheduling a limited number of social messages to promote your content on social networks.

    In addition, the commercial version also includes automatic social promotion on social networks, and other features to manage the entire editorial process.


  2. Li-An

    Well, more frustrating is when you don’t have any answer of the developer…who works for Automattic.


  3. Kingsley Felix

    This is so sad, we use this in 4 of our site..


  4. Paul Gibbs

    Edit Flow died about 6 years ago — Automattic wouldn’t let Daniel Bachhuber maintain it after he left that company; if my memory’s correct, he wrote it when he was part of the WordPress.com VIP team, which is where I met him. :)


    • Sonja London

      Very disturbing to hear this, especially since Daniel Bachhuber is still listed.

      Sad to see this level of neglect by Automattic on many plugins that have large numbers of users.

      Even worse that they will not even accept help from the community!


  5. R Scott LaMorte

    Oasis Workflow is another great alternative.




  6. Sajan Kota

    Edit Flow Plugin was a great for team collaboration. This plugin has always helped us in managing multi author WordPress website. Sad that automattic is discontinued the active development of this plugin. we have used this many of our client websites.


  7. Nick Gernert

    I head up VIP here at Automattic and appreciate posts like this that allow us to bring to light areas of confusion. I want to help clarify a few things! I’ll start by saying we are in no way dropping support for Edit Flow.

    We do see a difference between active feature development and maintenance updates to a plugin and this post tends to use these things interchangeably. It is correct that we are not currently pushing new features for Edit Flow. However, we are committed to maintaining this and other plugins so that those who depend on them are able to continue to do so.

    We face the same challenge that many in software face when it comes to supporting existing work while looking to the future and where to invest energy. I hope folks can understand the delicate balance here. We accept that we have fallen short at times when it comes to maintaining our existing work and appreciate the community holding us accountable.

    These are interesting times for us at VIP. We are seeing demand for WordPress in the enterprise market like never before. VIP is more committed than ever to product development for the unique needs of this space. We have recently brought on a new Head of Product and Engineering. With the addition of this role, there is a commitment to focused product development and that includes ensuring key plugins like Edit Flow are maintained. Presently, that maintenance includes security updates, critical bugs, ensuring compatibility with new versions of WordPress, and directly supporting VIP customer use. Going forward the VIP Product and Engineering teams are committed to allocating time to regularly review and address issues and provide regular updates to the plugins. As we stabilize on maintenance, new feature development will pick up in areas where we see unique opportunity.

    If you have specific issues with any of our plugins which are impacting your use, please do let us know in the forums or flag me personally. I’m ng at automattic.


    • James Leslie Miller

      It doesn’t seem like it’s even being given a level of attention at the most basic level of what could be considered “maintained”.

      This plugin was breaking functionality of other plugins on a client site.

      I forked the repo, fixed the issue, and submitted a PR on January 26 (https://github.com/Automattic/Edit-Flow/pull/499). After several months of periodic commenting and asking if anybody was even maintaining the repo, it finally got merged just last month (thanks, Viktor Szépe and Rebecca Hum!).

      This doesn’t seem to me like a commitment to maintaining the plugin.


  8. Auguro

    It’s simple, that plugin has to disappear/die because if conflicts with “Gutenberg Phase 3 (2020): collaboration, multi-user editing of Gutenberg, and workflows”.


    • James Leslie Miller

      I think that’s completely reasonable. I welcome a first-party solution. But I’d also appreciate just a basic maintenance-level of support for Edit Flow until that solution is actually implemented.


  9. Paul Walker

    Please see my comments here


Comments are closed.

%d bloggers like this: