[support] Having two versions ("last published" and "next release draft") of same content

[Cog Rusty]

Take a look at the http://drupal.org/project/revision_moderation
module if you haven't already. It leaves the current revision
published while the new one goes into moderation. Dupal 5 only.

If you don't want to give the reviewers the permissions required by
this module, another way is to forget about revisions and create new
nodes for the drafts, perhaps controlling access with taxonomy.



On Tue, Apr 22, 2008 at 7:08 PM, Daniel Caillibaud <ml.dcailli at free.fr> wrote:
> Hi all,
>
>  With drupal 6 (I can use 5.7 if easier), what is the best way to have two versions ("last published" and "next release
>  draft") of the same content ?
>
>  It's content of my own type (build with cck, each content have many fields and several files attached). I would like to
>  have all the published versions on the public website, and the draft of each content accessible for authentificated user.
>  In brief, it's a bit like implementing for contents mechanisms usually used for sowftware development (with the "still
>  in development" branch and the "stable" branch).
>
>  I guess I have to code a way to duplicate content from the "workspace" to public website (to always keep the current
>  working version in the "workspace"), but I'm starting with drupal so it's perhaps a crzy idea...
>
>  Every good advice will be apreciated.
>
>  Thanks
>
>  Daniel
>
>  PS: Next steps are to have a collaborative way to publish (more than X% agree without veto), and have different variants
>  of each content, with relations between variants ;-)
>  --
>  [ Drupal support list | http://lists.drupal.org/ ]
>