| Summary | Clicking "permissions" can make the datasource unavailable |
| Queue | Gollem |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | roel (at) gloudemans (dot) info |
| Created | 12/15/2005 (7205 days ago) |
| Due | |
| Updated | 02/16/2006 (7142 days ago) |
| Assigned | 02/12/2006 (7146 days ago) |
| Resolved | 02/16/2006 (7142 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
in the first place (it was a code submission) and I have little
familiarity with our permissions system.
State ⇒ Feedback
Priority ⇒ 1. Low
fatal error. Personally, I think that admins need to be aware of what
they're doing. To help that, I've added a warning-level notice when
permissions are created. I'd like to resolve this now; any objections?
Version ⇒ HEAD
Queue ⇒ Gollem
gollem/permissions.php. The only solution I could think of is adding a
confirmation page in permissions.php that requests a confirmation if a
permission should be created before redirecting to admin/perms/edit.php.
Priority ⇒ 3. High
permissions results in:
Fatal error: Call to undefined function: getname() in
/usr/share/php/Horde/Perms/datatree.php on line 271
Taken from Michael Slusarz
Version ⇒ HEAD
Queue ⇒ Horde Framework Packages
State ⇒ Feedback
since one month?
I noticed this in other applications too. If you go to admin interface
and _view_ permissions, you will not be able to send new email
anymore, or create new folders. You need to fill in these permissions
with something other then null, and wuola - it works again.
It never happened before. Just in HEAD of ~1 month old.
State ⇒ Assigned
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Queue ⇒ Gollem
Summary ⇒ Clicking "permissions" can make the datasource unavailable
Type ⇒ Bug
1) You are administrator
2) You have no permissions set on the data source (permissions are set
on Gollem, but there are no child permissions for the data source)
If you now click the permissions button from the top-menu, a child
node in the permission tree for the data source you were working in is
created. The default rights is to disallow everything. If you do not
set the rights to allow your users cannot access the datasource.
Yesterday, one of my fellow administrators was trying to set
permissions on a file. Because the permissions button in the top bar
attracts the attention much more than the "chmod" entry from the
actions menu the clicked the permissions button. The he saw that he
was not where he wanted to be and het clicked the "back" browser
button. The effect of this was that all users were thrown out of the
data source.
There are a few solutions possible:
1) Don't show the permissions button
2) Rename it
3) Create a separate gollem administration page
4) Make sure that the child permission node is not automatically
created when the permissions button is clicked