Closed (won't fix)
Project:
Drupal core
Version:
x.y.z
Component:
node system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Sep 2005 at 16:07 UTC
Updated:
8 Sep 2006 at 20:38 UTC
Jump to comment: Most recent file
Comments
Comment #1
killes@www.drop.org commentedI am at it.
Comment #2
killes@www.drop.org commentedHere is a quickfix which removes the offending function. The feature it was trying to implement was made impossible by the revisions patch. :-/
I suggest moving the "moderate" column from the node to the node_revisions table and then add the feature back.
The patch also fixes an input validation error in the export function.
Comment #3
dries commentedCommitted to HEAD.
Comment #4
gerhard killesreiter commentedHow should we procede with the "multiple active versions" feature that used to exist in the book? Consider it scrapped? Rework it somehow?
Comment #5
Uwe Hermann commentedWhat's the status on this one?
Comment #6
killes@www.drop.org commented"nobody cared enough". In principle it should be possible for a moderation module to track updates , get the proviously active revision, set that to active again, and display the new revision in its queue.
Comment #7
chx commentedapparently noone cares enough.