6.0.0-beta1
7/4/25

[#12208] Horde_Registry::removeUserData doesn't remove prefs
Summary Horde_Registry::removeUserData doesn't remove prefs
Queue Horde Base
Queue Version Git master
Type Bug
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester manuel (at) mausz (dot) at
Created 04/23/2013 (4455 days ago)
Due
Updated 05/16/2013 (4432 days ago)
Assigned 05/08/2013 (4440 days ago)
Resolved 05/16/2013 (4432 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
05/16/2013 05:27:17 PM Michael Slusarz Comment #6
State ⇒ Resolved
Reply to this comment
Horde_Prefs 2.4.1.
05/16/2013 05:27:03 PM Git Commit Comment #5 Reply to this comment
Changes have been made in Git (master):

commit 254c62393873e3906f04905bdc277dec34f29c49
Author: Michael M Slusarz <slusarz@horde.org>
Date:   Thu May 16 11:02:41 2013 -0600

     [mms] Fix removing prefs from storage backends (Bug #12208).

  framework/Prefs/package.xml |    2 ++
  1 files changed, 2 insertions(+), 0 deletions(-)

http://git.horde.org/horde-git/-/commit/254c62393873e3906f04905bdc277dec34f29c49
05/15/2013 01:24:05 PM manuel (at) mausz (dot) at Comment #4 Reply to this comment
sorry for late reply.
Patch looks good and works as expected. No more preferences left over.
05/08/2013 05:46:32 AM Michael Slusarz Comment #3
Assigned to Michael Slusarz
State ⇒ Feedback
Reply to this comment
Does this fix?
05/08/2013 05:46:13 AM Git Commit Comment #2 Reply to this comment
Changes have been made in Git (master):

commit 1b82259c61abd9319cd082675acf1f4e95b2a50e
Author: Michael M Slusarz <slusarz@horde.org>
Date:   Tue May 7 23:44:41 2013 -0600

     Possible fix for Bug #12208

  framework/Prefs/lib/Horde/Prefs/Scope.php |    4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)

http://git.horde.org/horde-git/-/commit/1b82259c61abd9319cd082675acf1f4e95b2a50e
04/23/2013 10:13:54 AM manuel (at) mausz (dot) at Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Horde_Registry::removeUserData doesn't remove prefs
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
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.

Saved Queries