Repository navigation
fix: Remove avatar and credentials only after user removal - #65435
Conversation
Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: Marcel Müller <marcel-mueller@gmx.de>
9e4a1e9 to
fe1be72
Compare
|
/backport to stable35 |
|
/backport to stable34 |
|
The backport to # Switch to the target branch and update it
git checkout stable34
git pull origin stable34
# Create the new backport branch
git checkout -b backport/65435/stable34
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick fe1be727
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/65435/stable34Error: Failed to check for changes with origin/stable34: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
This pull request has been automatically locked because it has been closed for more than 7 days. As we do not monitor merged or closed pull requests, we are locking this pull request to prevent further comments from getting lost in the noise. |
Summary
When deleting a user, we already call
$avatarManager->deleteUserAvatar($this->uid);, which removes the avatars after the user was deleted. Additionally we had a before listener, which removed the avatars before a user was actually deleted. This (alongside the removal of credentials) is tricky when the userbackend denies the user deletion (e.g. LDAP with an active user).How to test:
occ user:delete <ldap-user>The specified user could not be deleted. Please check the logs.Checklist
3. to review, feature component)stable32)AI (if applicable)