[Tickets #12208] Horde_Registry::removeUserData doesn't remove prefs

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/12208
------------------------------------------------------------------------------
  Ticket           | 12208
  Erstellt Von     | manuel at mausz.at
  Zusammenfassung  | Horde_Registry::removeUserData doesn't remove prefs
  Warteschlange    | Horde Base
  Version          | Git master
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


manuel at mausz.at (2013-04-23 10:13) hat geschrieben:

Calling removeUserData() on a user doesn't remove its preferences.  
Instead all associated prefs are restored to their default values.

removeUserData() calls $prefs->remove() which deletes (or will delete,  
see #12207) the prefs from the database. Furthermore all prefs get  
reset  to their default value and the dirty flag gets set. This  
behaviour causes the preferences shutdown handler to restore the prefs  
inside the database with their associated default values.

We use this function to wipe all userdata from the database. My  
current fix is to call $prefs->cleanup(true) afterwards. This will  
wipe the cache the shutdown handler uses.