Summary | can not remove user data when deleting user |
Queue | Nag |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | vilius (at) lnk (dot) lt |
Created | 06/23/2008 (6190 days ago) |
Due | |
Updated | 06/30/2008 (6183 days ago) |
Assigned | 06/28/2008 (6185 days ago) |
Resolved | 06/28/2008 (6185 days ago) |
Milestone | |
Patch | No |
going on. First we were never even attempting to delete the actual
share, just the data in Mnemo and Nag. Second, we were not removing
shares...
that was causing only the share data itself, and not the user or
group perm data to be deleted when removing a share...all have
(hopefully) been fixed.
this under
bug 6998.Also filled another related issue under
bug 6999.All tests were performed on FW_3 code.
Assigned to Michael Rubinsky
State ⇒ Resolved
going on. First we were never even attempting to delete the actual
share, just the data in Mnemo and Nag. Second, we were not removing
any permissions the removed user may have had in *other* user's
shares...and finally, there was a bug in the SQL Horde_Share driver
that was causing only the share data itself, and not the user or group
perm data to be deleted when removing a share...all have (hopefully)
been fixed.
http://cvs.horde.org/diff.php/framework/Share/Share/sql.php?r1=1.35&r2=1.36&ty=u
http://cvs.horde.org/diff.php/mnemo/lib/api.php?r1=1.87&r2=1.88&ty=u
http://cvs.horde.org/diff.php/nag/lib/Nag.php?r1=1.173&r2=1.174&ty=u
http://cvs.horde.org/diff.php/nag/lib/api.php?r1=1.184&r2=1.185&ty=u
State ⇒ Assigned
actual data from backend is not cleared for nag and mnemo.
[nag|mnemo]_shares and [nag|mnemo]_shares_users are still populated.
In Turba on the other hand, data is removed from turba_shares but NOT
from turba_shares_users.
State ⇒ Resolved
http://cvs.horde.org/diff.php/nag/lib/api.php?r1=1.182&r2=1.183&ty=u
Taken from Michael Rubinsky
Version ⇒ HEAD
Queue ⇒ Nag
since this is not an issue with any of the share drivers.
be the problem.
as the favourites driver, or even any virtual address books you will
get the error I'm referring to. Check the logs after applying the
error logging changes, the Turba error should be gone.
That being said, that's not the root of the problem. The problem is
not specific to the sql share driver. The issue is that when you are
deleting a user in Nag, for instance, the Nag::listTaskList() method
always checks perms for the *currently logged in* user, not the user
who you are deleting...so the task list is not returned. These
methods need to be changed to allow filtering perms for other users as
well.
the problem.
State ⇒ Assigned
Assigned to Michael Rubinsky
case of Turba, it is most likely being caused by a source that does
not support removing user data. I added some error logging, and
(temporarily?) removed the error flag in this case...
not sure about the other apps yet, still digging.
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Summary ⇒ could not remove user data if using SQL share backend
Type ⇒ Bug
Queue ⇒ Horde Framework Packages
share backend is used.
Turba fails with: There was an error removing an address book for username
Nag and others fail with: Permission Denied