diff options
| author | Gunnar Wrobel <wrobel@pardus.de> | 2009-03-20 10:22:10 (GMT) |
|---|---|---|
| committer | Gunnar Wrobel <wrobel@pardus.de> | 2009-03-20 10:22:10 (GMT) |
| commit | e3abbd6e4f9176c7031c43473aeb2592a54fee21 (patch) | |
| tree | 8b45eecf08cbdf1c6ccc5dd6d46564c6942f28fe | |
| parent | fe85a712d6a749e6efaffcc7db4e571b8a6c68db (diff) | |
| download | perl-Kolab-2.2-feature-suc.tar.gz | |
kolab/issue3472 (web client user prefs not deleted when user gets deleted)2.2.22.2.12.2-feature-suc
| -rw-r--r-- | lib/Kolab/LDAP.pm | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/lib/Kolab/LDAP.pm b/lib/Kolab/LDAP.pm index 8299ba7..be87b43 100644 --- a/lib/Kolab/LDAP.pm +++ b/lib/Kolab/LDAP.pm @@ -710,6 +710,18 @@ sub deleteObject } } + # FIXME + # This is a horrible fix for kolab/issue3472. kolabd is a simple + # deamon that should react to changes within LDAP. It should NOT + # however have any application knowledge. It would be better if + # each application that requires cleanup operations after user + # removal could add a script in a directory collecting such + # operations. + if (-e $Kolab::config{'webserver_document_root'} . '/client/storage/' . $uid . '.prefs' ) { + unlink($Kolab::config{'webserver_document_root'} . '/client/storage/' . $uid . '.prefs'); + Kolab::log('L', "Deleted web client user preferences for user $uid.", KOLAB_DEBUG); + } + if (!$uid) { Kolab::log('L', 'Deleted object not found in mboxcache, returning', KOLAB_DEBUG); return; |