Open dkobia opened 12 years ago
Deathshiver
commented
12 years ago We should consider replacing the "site settings" menu button with a small admin panel button that will contain the features in the enhanced posted above as well as site management and settings.
ekala
commented
12 years ago Just realized that deleting a user does not delete their buckets, rivers, collaborations and subscriptions etc. In a nutshell, when a user is deleted from the system, destroy all their data.
69mb
commented
12 years ago Don't think we should delete data from the DB especially due to the havoc it causes with indexes.
Alternatively we should have a deleted column if deletion is an absolute must otherwise just have disabled.
dkobia
commented
12 years ago Maybe just tag a bucket or river as deleted? Deleting the rivers and buckets would leave those pivot table entries with orphans, unless we cascade the actions and add constraints to that effect on the pivot tables.
Deathshiver
commented
12 years ago Just curious, in what legitimate case would we ever delete a user? For the purpose of maintaining logs and information, shouldn't we always have access to such user data even if the user can no longer log in? Just mark the user as "closed" or "banned". Any contributions they make to the system should not be deleted either.
ekala
commented
12 years ago In which case, I'll go ahead and undo this - c058e44b8df2471c96ae4407ebcec3f0d1c454c5
Sure, it makes sense to have something like account_status field in the users table which can be used keep tabs on status of a user account e.g. disabled, banned, suspended etc
We need a way for administrators to view all the users in the system along with how many rivers and buckets they have. In addition, we need to be able to regulate how many rivers a user can have along with turning access of and on.