Comments on: Edit Flow v0.5: Introducing the editorial calendar

By: Robby Slaughter

Robby Slaughter — Sat, 26 Mar 2011 22:57:13 +0000

Never mind; I accidentally had an older version of Edit-Flow installed and it looked like I had a workaround.

The current version does seem to work well with WordPress 3.1

Feel free to delete this comment thread.

By: Daniel Bachhuber

Daniel Bachhuber — Sat, 26 Mar 2011 18:58:08 +0000

Robby, can you create a new thread in the WordPress.org forums for this? I’m not quite sure what you’re referring to.

By: Robby Slaughter

Robby Slaughter — Sat, 26 Mar 2011 18:55:30 +0000

It appears if you just change the word “Search” to the word “Query” in that one line of code, your plugin is compatible with WordPress 3.1.

Please check this and update it. Thanks!

By: Daniel Bachhuber

Daniel Bachhuber — Fri, 25 Mar 2011 00:48:41 +0000

Thanks! Let us know if there are any features Editorial Calendar had that you think are missing from Edit Flow. We’re always happy to entertain feature requests

By: Corey Pein

Corey Pein — Sat, 05 Mar 2011 17:12:23 +0000

Awesome job on this.
The ‘editorial calendar’ plugin was locking up my admin panel. This is a major improvement in concept and execution.

By: Daniel Bachhuber

Daniel Bachhuber — Mon, 20 Dec 2010 14:55:29 +0000

Not yet… Could you explain better what you need in the support forums?

By: Rosie

Rosie — Fri, 17 Dec 2010 15:35:54 +0000

I was wondering if there was a follow-up blog post tto David’s question regarding enabling the custom status dropdown without the publish_post capability? Thanks!

By: Mo Jangda

Mo Jangda — Tue, 05 Oct 2010 19:34:55 +0000

Thanks for your comment Lance! And a good point on adding times to the calendar. We’ll see if we can work it in for an upcoming release.

By: Mo Jangda

Mo Jangda — Tue, 05 Oct 2010 19:33:57 +0000

Thanks for your comment David; glad you like the plugin!

This is a limitation on the WordPress side; like you point out, only users with the publish_post capability can see the custom status dropdown. We’ve had this request from a number of people and there is a workaround for this, but it’s not the most elegant thing in the world. I’ll write up a blog post on how to do this in the next few days.

On the upside, there are some changes planned in the next version of WordPress that should hopefully make it easy to have better control over who can access what statuses and so on.

By: Mo Jangda

Mo Jangda — Tue, 05 Oct 2010 19:28:56 +0000

Thanks for bringing this up! Looks like some changes were made to core for 3.1, which dropped the WP_User_Search class and the reason why it’s throwing the error. We’ll have to make some changes on our end to support this.

For now, I’d say stick to 3.0.x