Workflow for "External" Contributors

[gregfuller]

Hi,

Here's the use case: Jane Doe is an external content contributor that can only set her own entries to draft. She creates a new entry. The super admin comes along and reviews it and sets it to publish. Now the entry is seen by users.

Jane discovers an error and edits the entry. The entry is now set back to draft, and must be re-published. The entry disappears from site. Users are wondering what happened to the entry, maybe they just made a comment to the entry, maybe they came back to read it in full, maybe they sent the link to a friend, etc.

A solution would be to somehow save a copy of the old version and continue to publish it until the new version was approved.

Is there a way to do this, and if not, what would be a good approach? I'm willing to try my hand at writing a plugin or modifying an existing plugin.

Thanks, Greg

[garvinhicking]

Hi!

Yes, workflows would be nice to have; we have this as a Feature request for some time now:

http://sourceforge.net/tracker/index.ph ... tid=542825

Any takers?

Some groundwork can be found in the serendipity "versioning" plugin - this could be taken, and the frontend could then only read the latest "approved" version from the blog, instead of the most "current" one.

HTH,
Garvin

[gregfuller]

I'll have to scratch my head a little more over this. After thinking it through, I see it getting fairly complex, moving revisions records into and out of the main entry table, or otherwise managing the coordination between the two.

Thanks,

Greg