http://drupal.org/node/50506

This might be a bug, or it might be a feature issue. In either case, a simple loop would implement a very useful behavior: if a node is pending moderation, but there is a previous rev that is not pending moderation, treat it as current for display purposes.

I intend to attempt a patch for this, if someone who really knows what is going on could comment on the tastefulness of this idea I'd be most grateful.

Comments

sepeck’s picture

sepeck commented
Status: Active » Closed (duplicate)

duplicate of http://drupal.org/node/38451

yched’s picture

yched commented
Version: 4.6.5 » x.y.z
Status: Closed (duplicate) » Active

sepeck : This is not a duplicate. The issue you mention is something else - that has been fixed in current HEAD.

See this forum thread or this comment for more info on this request.

In short (from the first link above) :

Is there any way of allowing a node to be edited but keeping the original version published until the admin approves the new one?

I'd say this is a must have.
In fact I've spent some time working on a site that relies on this (rather obviuous ?) workflow pattern, being quite confident that this could be done easily, and I just found out that Drupal didn't handle it.
I find that surprising considering how mature other parts of Drupal are.

(nb : I know the stuff about Open Source developpement and the notion of "developped if needed/funded/someone has the time and will to do it".
I'm not ranting/complaining/blaming anyone here, I'm just saying I'm surprised that Drupalers could live without it for so long. Whatever.)

bmargulies : I'm also thinking about working on a patch myself.
On the good side :

  • patch 38451, that landed in HEAD last september, makes the way much clearer

On the bad side :

  • Implementing this fonctionnality will most certainly require a database change (at least : publication status per revision, as opposed to per node), and probably rather heavy core code rewriting - and debugging.
  • It's too late now for such a patch to make it in the upcoming 4.7...
    But it would probably be a pity that 4.8 went out without it.
mattgrayson’s picture

mattgrayson commented

http://drupal.org/node/48731 has a patch that looks like it might make some headway towards solving this issue. Unfortunately, I haven't been able to get it to work right against the latest CVS version.

I agree heartily with yched though - this seems like functionality that should be a no brainer wrt revisions.

yched’s picture

yched commented
Status: Active » Closed (duplicate)

See http://drupal.org/node/48731, and eventually Webchick's revision_moderation module.