[Tickets #7794] more info in permissions for child perms. "Maximum Number of * ITEM (max_*)"

bugs at horde.org bugs at horde.org
Sat Dec 20 19:52:03 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7794
------------------------------------------------------------------------------
  Ticket             | 7794
  Created By         | b5b5b5b5 at centrum.sk
  Summary            | more info in permissions for child perms. "Maximum
                     | Number of * ITEM (max_*)"
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          | next one
  Patch              |
  Owners             |
------------------------------------------------------------------------------


b5b5b5b5 at centrum.sk (2008-12-20 14:52) wrote:

Hi.
As i've been testing my first horde + modules/projects enviroment, and  
i found that there is a lack of info's in the "Add a child permission  
to *ANY*" form.
In any form alike, and in any sub-form "All Authenticated Users |  
Guest Permissions | Creator Permissions | Individual Users | Groups"  
of them.
To be more precise, there are absolutely none.

There is just one empty field. And that is the problem. I don't know  
how other people, but my experience from other applications is that,  
when field is empty, then the value is e.g. UNLIMITED.
In entire Horde projects - including basic framework, when you left it  
empy as I did, i thought it will be just unlimited as i've mentioned  
before.
After that, i was unable to create any new ITEM in e.g. kronolith, nag, mnemo.
Then IRC at mrubinsk directed me to permissions, where i tryied just to  
remove that child perms., which helped.

So it would be good to put there some info for others to avoid similar  
problem, something like, "if field is empty, it will disable the  
ability to create new *ITEMS* - remove this child permissions or enter  
some number", or maybe somehow in the code forbid to left that field  
empty, or insert there any default number like 100 , that it will make  
sure it won't make any problem. + info's of course.

Daniel






More information about the bugs mailing list