We had a recent issue where our Marketing department published poorly worded content on our website and people were a bit annoyed the content was not run past our Editorial department. I jumped up and said, “Hey, our CMS can manage that” and went about implementing a new custom status, “Review”. I then configured the “Open” status to now only be accessible to the Editorial department, and “Review” and “Closed” are available to everyone.

So, the next day, someone in Marketing went to edit something, and when they saved it, it was set to “Closed”. They could have chosen “Review” from that menu, but alas, the same result. The existing content was immediately removed from the website.

Is it possible to do this in such a way that if existing content is edited, the last revision stays public on the website? Otherwise, how can you use status-based publishing to edit pre-existing content?

I highly recommend better workflow http://devot-ee.com/add-ons/better-workflow

I highly recommend better workflow http://devot-ee.com/add-ons/better-workflow

Is a third party product required to accomplish this? Is the experience I’m having “as good as it gets” without a plugin?

We started with ee 1.5.2 and had to write in house customizations - so for us, add-ons have been an enormous advantage. better workflow and low variables are indispensible for robust websites.

jaydisc - 05 July 2012 08:21 AM

Is a third party product required to accomplish this? Is the experience I’m having “as good as it gets” without a plugin?

Module, actually and probably an extension…but that’s being picky..

With EE the content is either on the site or off.  There is no native notion of content versioning where one version is live and another is working through a review process.  For the latter you’ll need an add-on, and Better Workflow is pretty much it for EE2 at this point.

OK. Thanks everyone.