Summary | Calendar Perms with Frombackend/tobackend hook |
Queue | Kronolith |
Queue Version | HEAD |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | jan (at) horde (dot) org |
Requester | grahamcw (at) hurleybulldogs (dot) com |
Created | 03/04/2008 (6322 days ago) |
Due | |
Updated | 09/22/2008 (6120 days ago) |
Assigned | 06/30/2008 (6204 days ago) |
Resolved | 09/22/2008 (6120 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
State ⇒ Resolved
http://cvs.horde.org/diff.php/horde/templates/shares/edit.inc?r1=1.44&r2=1.45&ty=u
http://cvs.horde.org/diff.php/kronolith/perms.php?r1=1.8&r2=1.9&ty=u
http://cvs.horde.org/diff.php/kronolith/templates/perms/perms.inc?r1=1.6&r2=1.7&ty=u
username@domain.name but to have them be able to refer on the front
end side to just username. This works fine as my perms are all
username@domain.name
I think reversing them will break this.
State ⇒ Feedback
exactly in the wrong direction. What happens if you exchange the
methods?
My Apology.
State ⇒ Feedback
bug #6333?State ⇒ Assigned
Priority ⇒ 1. Low
State ⇒ Unconfirmed
New Attachment: k-perms.patch
Queue ⇒ Kronolith
Summary ⇒ Calendar Perms with Frombackend/tobackend hook
Type ⇒ Bug
I was changing permissions to a shared calendar.
I entered someusername as user and set permissions and saved permissions
then went to add another - someusername2 - when I save permissions
my existing someusername shows up , but also a new
someusername@mydomainname .
I add a third user someusername3
and I end up with these usernames
someuername
someusername@mydomainname@mydomainname
someusername2
someusername2@mydomainname
someusername3
so now I go to delete everything and add them to a group -
I clear all the permissions on all the names names
but all 3 origionals names stay there
someusername
someusername2
someusername3
Looks like kronolith/templates/perms/perms.inc is not consistently
unhooking $users
Patch attached