Tickets :: [#8754] horde.removeUserDataFromAllApplications does not call removeUserData for every application

6.0.0-beta1

12/21/25

Summary	horde.removeUserDataFromAllApplications does not call removeUserData for every application
Queue	Horde Base
Queue Version	FRAMEWORK_3
Type	Bug
State	Resolved
Priority	1. Low
Owners
Requester	Valentin.Vidic (at) carnet (dot) hr
Created	12/07/2009 (5858 days ago)
Due
Updated	12/07/2009 (5858 days ago)
Assigned
Resolved	12/07/2009 (5858 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	Yes

12/07/2009 06:31:16 PM	Michael Rubinsky	Version ⇒ FRAMEWORK_3 Queue ⇒ Horde Base

12/07/2009 06:30:51 PM	Michael Rubinsky	Comment #3 State ⇒ Resolved	Reply to this comment
tweaked and committed, thanks!

12/07/2009 06:30:22 PM	CVS Commit	Comment #2	Reply to this comment
Changes have been made in CVS for this ticket: Registry#hasMethod() returns the app name, not boolean true on success. ~~Bug: 8754~~ Submitted by: Valentin (dot) Vidic (at) CARNet (dot) hr http://cvs.horde.org/diff.php/horde/lib/Attic/api.php?rt=horde&r1=1.43.2.16&r2=1.43.2.17&ty=u

12/07/2009 03:52:20 PM	Valentin (dot) Vidic (at) carnet (dot) hr	Comment #1 Priority ⇒ 1. Low New Attachment: api.diff Patch ⇒ Yes Milestone ⇒ Queue ⇒ Horde Groupware Webmail Edition Summary ⇒ horde.removeUserDataFromAllApplications does not call removeUserData for every application Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
While testing user delete via api calls I discovered that $app.removeUserData doesn't get called at all and user data stays in the database. The problem seems to be that the call to $registry->hasMethod($api . '/removeUserData') doesn't return true or false, but application name or false. Attached patch fixes this check.