Ferdinand Thiessen 5d5c307a1a fix: Make user removal more resilient ... Currently there is a problem if an exception is thrown in `User::delete`, because at that point the user is already removed from the backend, but not all data is deleted. There is no way to recover from this state, as the user is gone no information is available anymore. This means the data is still available on the server but can not removed by any API anymore. The solution here is to first set a flag and backup the user home, this can be used to recover failed user deletions in a way the delete can be re-tried. Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>		2024-10-15 16:50:27 +02:00
..
AvailabilityCoordinatorTest.php	enh(userstatus): add OOO automation and remove calendar automation	2023-11-28 10:28:06 +01:00
AvatarUserDummy.php	Fix multiline comments	2020-04-08 22:24:54 +02:00
Backend.php	Format code to a single space around binary operators	2020-10-05 20:25:24 +02:00
DatabaseTest.php	fix!: Remove symfony EventDispatcherInterface from User	2023-07-27 23:13:37 +02:00
Dummy.php	Format code to a single space around binary operators	2020-10-05 20:25:24 +02:00
ManagerTest.php	fix(users): Don't crash if disabled user is missing in the database	2024-09-23 18:08:17 +02:00
SessionTest.php	fix(users): Don't crash if disabled user is missing in the database	2024-09-23 18:08:17 +02:00
UserTest.php	fix: Make user removal more resilient	2024-10-15 16:50:27 +02:00