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

[Andy Wright]

Michael Rubinsky wrote:
>
> 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.
>
>
Mike, thanks for the explanation - what I'm seeing makes more sense now.

Unfortunately the "non-shared"source holds the users' personal address 
books so I can't drop that. I guess the next obvious question is to ask 
if there is a way to stop Turba from creating the default share on the 
Shared source? Or failing that, a way of hiding a share from users?

I did consider trying to export each user's personal book and import 
that into the newly created user-share, but many of them have set up 
Lists which don't export/import :(

Thanks again,
Andy.