[Tickets #2245] Horde Share implementation for Turba

[bugs@bugs.horde.org]

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

Ticket URL: https://dev.horde.org/horde/whups/ticket/?id=2245
-----------------------------------------------------------------------
 Ticket             | 2245
 Updated By         | Michael Rubinsky <mrubinsk at horde.org>
 Summary            | Horde Share implementation for Turba
 Queue              | Turba
 Version            | HEAD
 State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | Michael Rubinsky
-----------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2005-07-18 20:07) wrote:

> This perms system hasn't been truly supported in a stable release 
> yet. No need to make allowances for that. IMO, of course.

Cool.  Sounds good to me...

>> 2 - Setting 'use_shares' => true isn't really the same as setting
>> 'public' => true.
>
> No, it's the same as setting 'public' => false on a SQL source. And 
> having 'use_shares' is a *much* clearer setting than public, imo.

Ah.  One of those forehead slapping moments...  It's amazing how clear some
things can become after you get a nudge in the right direction ;)

A related question - If we are using Shares for permission setting on a
source, is there a way to still allow setting max_contacts without allowing
source level permissions to be set?  I can see a problem with it *looking*
like you can set read/write permissions from the permissions UI...which, of
course, would be ignored by turba.  I can filter out the source from
appearing in the permissions UI, but then we loose the ability of letting an
administrator set the maximum number of contacts.