21 Jul
2006
21 Jul
'06
5:26 p.m.
workflow + actions in core could be an option. Have a workflow state for deleted, on state change to deleted, do action delete. yet another option.
+10. This is the solution we should get behind. Dries has targeted workflow+actions for next version. It's flexible. It's an API. There are a bunch of actions out there already (and they're easy to write). As part of "core" install profile, we could add a reasonable default workflow (with states like "unpublished" -> "published" -> "deleted/archived"). As to checking the "deleted" field. This can happen using hook_sql_rewrite. Any legit query looking at nodes should be calling this hook anyway. Also: this allows for the deletion to live in contrib, which sounds like what people want. -M