Closed (duplicate)
Project:
Scheduler
Version:
master
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 Jan 2008 at 16:40 UTC
Updated:
29 Jun 2008 at 17:48 UTC
I would love scheduler to be able to complete delete a node when it expires.
Comments
Comment #1
syngi commented*completely delete
and the ability to choose between unpublishing and deletion per node type.
Comment #2
eric-alexander schaefer commentedFeatures like this need to go into HEAD.
We could combine it with #137802: Scheduler un- and publish splitted out. One would allow publishing, unpublishing and deletion per node type and there would be a separate delete_on field. How about that?
Comment #3
skiminki commentedYeah, if we want this feature, this most certainly needs to be combined with #137802: Scheduler un- and publish splitted out. I really wouldn't want to expose scheduled delete when publish and unpublish suffice.
You know, I'm thinking that maybe we shouldn't implement scheduled delete feature at all. Instead, we should look into supporting actions-module (comes with D6 by default) and implement scheduled action. That way we could make any node-specific action schedulable, including delete. This would offer real flexibility to the users.
Comment #4
eric-alexander schaefer commentedGood point. I was just thinking about a universal scheduling infrastructure. I didn't look into D6 very deep though. If it can be done with actions, we should even consider transforming publish and unpublish into actions.
Comment #5
eric-alexander schaefer commentedPlease followup to #276376: Make scheduler more generic? which would implement this feature in a generic fashion.