How is this different than "unpublishing" a node? Perhaps the Delete button should become an Unpublish button. Then an admin would use the regular admin interface if a node needed permanent deletion. Farsheed --- sime <info@urbits.com> wrote:
I agree with Mark.
As some probably know. Many systems never delete anything from the database. In my case, these systems were in the Pharmaceutical Industry where everything needs to be 100% audited (http://www.21cfrpart11.com). So what IT called deleted, was actually just a flag in a column and no "user" could see these items without going through the approved and tested workflows.
So just for the record, I would like a "deleted" column in Drupal.
Preferably it would be something I don't have to think about. The db layer could automatically adjust incoming SQL to filter out the deleted records, hence existing code would not need changing. Alternatively, querys that need to access deleted records could pass an additional variable to say so.
Simon
mark burdett wrote:
We need to prevent users from deleting their nodes. They can discontinue (unpublish), but not delete them. (We want the node data to still be in the database, not just in a restorable trashbin). Would be good to allow for this kind of configuration.
--mark
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com