[development] Implementing a user deletion policy

Adam Gregory arcaneadam at gmail.com
Mon Apr 5 15:59:17 UTC 2010

Using hook_form_alter you can intercept/modify the delete button.
Adam A. Gregory
Drupal Developer & Consultant
Web: AdamAGregory.com
Twitter: twitter.com/adamgregory
Phone: 910.808.1717
Cell: 919.306.6138

On Mon, Apr 5, 2010 at 11:54 AM, Dave Reid <dave at davereid.net> wrote:

> Steve,
> Might want to checkout something like
> http://drupal.org/project/userprotect where you wouldn't have to touch any
> code at all.
> In addition, watchdog messages should show the currently logged in user
> when the message was fired. That would be the person who deleted the
> account.
> Dave Reid
> dave at davereid.net
> On Sun, Apr 4, 2010 at 11:00 AM, Steve Yelvington <steve at yelvington.com>wrote:
>> We ran into a problem involving deleted accounts, so I'm looking into
>> implementing some tighter controls. However, it doesn't appear that
>> user_delete() is a hook, so I can't intercept it. I suppose I can filter out
>> the "delete" button, but are there any other obvious solutions? I don't want
>> to kill any kittens.
>> Also, Watchdog logs the deletion but not the ID of the user who deleted
>> the account. Seems like an oversight.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20100405/98b9bde8/attachment.html 

More information about the development mailing list