Generally speaking, an event that has already happened is no longer of any interest. However, at present (I'm using the 4.5.0 version for the moment, but 4.6 appears to have the same functionality), there is no mechanism for removing old events from the database. This means that if I click on a type of event, I get a list of all the events in the database including ones that are long past.

I would like to propose a cron job which would remove past events automatically. I have described some thoughts about this here.

One might add to this suggestion the possibility to exclude past events from being removed.

Opinions on this would be welcome.

Comments

killes@www.drop.org’s picture

killes@www.drop.org commented

use scheduler.module

joel_guesclin’s picture

joel_guesclin commented

Having looked at the scheduler module briefly, I have a problem with it: it automatically includes its unscheduling dates in EVERY node, and it requires that the editor choose an unscheduling date seperately from the event date.

This has two serious drawbacks IMHO:
1) I'm trying to keep the node editing interface (used for articles) as light as possible - since the scheduling will only be used for events in my case then it is a non-starter for me to include these extra boxes in every node
2) You have to put in two different dates: event date and unscheduling date. This leaves us wide open to error on the part of the editor (eg unscheduling before the event).

So, I will probably put in some work on events myself and propose a patch.

f1wade’s picture

f1wade commented

does anyone have any more on this?
i have the same issue i would like to be able to remove all events before a set date, and have it only accessable to an administrator.
can anyone tell me how to do this please ?