[turba] Confusion using /turba/scripts/upgrades/public_to_horde_share script

[Michael Rubinsky]

Quoting Andy Wright <horde at eltofts.homelinux.com>:

> However, with "Shared address book", each user can only see entries for
> which they are the owner. Using the permissions facility in Horde to
> add all rights all the way down the turba tree (Address book, Sources
> and localsql2) has no effect on what users can see.

Correct, the permission system only sets permission on a per-source  
basis, not per object.

> Having given up on the permissions route, I tried to use the
> public_to_horde_share script and then set use_shares=>true on the
> "localsql2" source.

This is correct.

> This works insofar as users can now see all entries in the shared book
> (I made myself owner of the share and gave all rights to all users for
> testing). However, there are now *2* shared address books - the
> original one as defined in sources.php (and to which users now see no
> entries, not even their own) and one listed under the name I gave
> during the upgrade, which works as expected. So now I see - "My address
> book", "Shared address book", "Shared address book - upgraded".

With current Turba code, for any source using a sql backend, the user  
is automatically given a 'default' share for any source with  
use_shares=>true.  So, what you are probably seeing is:

"My address book" -> the address book from the localsql source.

"Shared address book" -> the user's default share from localsql2.   
This is a personal address book owned by the user, but the user can  
set perms on this via the "My Address Books" page.

"Shared address book - upgraded" -> This (as is probably obvious to  
you) is your upgraded address book.

The basic idea was to allow people with a set up similar to yours  
(with two seperate turba_objects tables) to implement shared address  
books along with personal address books using the same turba_objects  
table.  So...unless you already have data in your 'non-shared' address  
books, I would recommend you just remove that from your config and  
only use the one sql source.


> Am I doing something wrong here? I just want to end up with one working
> shared address book - not one that works and one that doesn't :)

I think you'll find that all the address books work - the additional  
shared address book will behave like a normal address book.

Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org