robchur wrote:

First problem would be that deleting any row in the users table would be unsafe,
as it leaves references to the user all over the place, which could cause all
sorts of wonderful errors.

Second issue is that you assume some sort of daemon/TSR which runs the software,
which isn't the case. This couldn't be 100% automated; either it would need to
be part of the index.php script (which increases server load) or you would need
to use a maintenance script, which defeats your objective of the process being
automated.

It is a nice idea, but as it stands, it would be problematic.

OK. Maybe that is good. Since this vision cannot be run like a daemon, it
doesn't necessarily have to be automated. There could be a special page e.g.
Deleteinactive that would do the work upon starting it (and would be available
to sysops only, naturally).

As for the database, I don't know how to sort that out...

alarm wrote:

Deleting users permanently is not acceptable in many cases - this cannot be undone, also mentioned problems with references. So a better
approach would be - disabling user accounts, so disabled user is not visible in user list, cannot login, but it is still visible in
referenced places (history, etc), and this can be undone by reenabling a user.

I like the idea, Andrius. It's even better. Someone willing to do it? :)

robchur wrote:

Closing as a duplicate of bug 6397, which is more feasible.

*** This bug has been marked as a duplicate of 6397 ***