Steve,<div><br></div><div>Might want to checkout something like <a href="http://drupal.org/project/userprotect">http://drupal.org/project/userprotect</a> where you wouldn't have to touch any code at all.</div><div><br>
</div><div>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.</div><div><br clear="all">Dave Reid<br><a href="mailto:dave@davereid.net">dave@davereid.net</a><br>
<br><br><div class="gmail_quote">On Sun, Apr 4, 2010 at 11:00 AM, Steve Yelvington <span dir="ltr"><<a href="mailto:steve@yelvington.com">steve@yelvington.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
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.<br>
<br>
Also, Watchdog logs the deletion but not the ID of the user who deleted the account. Seems like an oversight.<br>
<br>
<br>
</blockquote></div><br></div>