[Liam W] (RIP) Member Self Delete

xF2 Add-on [Liam W] (RIP) Member Self Delete 2.0.5 Patch Level 5

No permission to download
Apologies all, in my tiredness last night I mis-assigned the new option to a different add-on. I really should've learned by now not to release updates in the early hours.

The option has been returned to it's rightful home with this version.
  • Added option to control whether to request a reason from users
    • Added option to control whether to require reason from users
  • Prevent possible error relating to options array by verifying option value
Note: After updating, please save your options for this add-on to update the stored value.
Fix incorrect logic which would cause pending deletions to be cancelled if the repeat deletion check was enabled
Changes in Beta 5
  • Improved resilience to invalid/unexpected data in database

Changes from Beta 4
  • Added upgrade step to normalise invalid data
  • Added the ability to set a 'multiple deletion delay', which will prevent users which have initiated a deletion in the past x days from scheduling their accounts for deletion again until that number of days have passed.
I honestly do not know how this cron entry keeps on returning. Spooky... Apologies, nonetheless.
Another second point jump, with a host of new features.

  • User criteria eligibility
    You can now set user criteria that must be met for users to be able to delete their accounts.
  • Permission
    There is now a user group permission to control who can delete their accounts. This is in addition to the user criteria above.
  • Disabled usergroup
    There is now an option to add a user to an additional user group when they've been disabled. This can be used to adjust the username styling for disabled users.
  • Bug fixes
    Many bugs have been fixed, including the erroneous date in completion emails.


  • 1567665981783.png
    827.6 KB · Views: 33
  • 1567665989516.png
    434.1 KB · Views: 36
There was a ghost cron entry in my development database... don't know how that happened. I've removed it from the beta 4 installer - sorry for the inconvenience.