yes, but i think it should be some info about it there, because when 
it's not, then new unaware people won't know

In this case, then '0' or 'empty' value is not having the permission 
at all.  In other words, if you don't want to limit the number of 
items a user can create, then don't add a max_* permission to begin 
with. A maximum count of 0 tasks should mean just that, the the user 
is not allowed to create any new tasks.

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@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