diff options
| author | Gunnar Wrobel <wrobel@pardus.de> | 2009-04-16 08:55:18 (GMT) |
|---|---|---|
| committer | Gunnar Wrobel <wrobel@pardus.de> | 2009-04-16 08:55:18 (GMT) |
| commit | c2e52f7d9ade935c84405249fe1d6ec801a2c914 (patch) | |
| tree | 8639f6f4b4dd770e186b6a8cce2a39ff3024c1ab /lib | |
| parent | c61273f97f643f07e4f4bd09d5cb91ec0524ef62 (diff) | |
| download | perl-Kolab-c2e52f7d9ade935c84405249fe1d6ec801a2c914.tar.gz | |
MFB: kolab/issue3472 (web client user prefs not deleted when user gets deleted)
cvs diff -u -d -r1.11.2.1 -r1.11.2.2 perl-kolab/lib/Kolab/LDAP.pm
cvs diff -u -d -r1.398.2.10 -r1.398.2.11 release-notes.txt
Diffstat (limited to 'lib')
| -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 4e1c07e..7acb2e0 100644 --- a/lib/Kolab/LDAP.pm +++ b/lib/Kolab/LDAP.pm @@ -721,6 +721,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; |