[turba] have everybody use public address book exclusively

Jan Schneider jan at horde.org
Mon Apr 27 06:45:36 UTC 2015


  Zitat von Sebastian Birnbach <birnbacs at gmail.com>:

> Looking at /var/log/messages it seemed that owner_id needs a default
> value on a database level:
>
> Apr 24 20:30:29 luna HORDE: [turba] SQL QUERY FAILED: Field 'owner_id'
> doesn't have a default value       INSERT INTO turba_objects
> (object_type, object_firstname,       object_lastname,
> object_nameprefix, object_namesuffix, object_email,      
> object_homeemail, object_workemail, object_homephone,      
> object_homephone2, object_workphone, object_workphone2,      
> object_assistantphone, object_homefax, object_cellphone, object_fax,
   
>   object_homestreet, object_homecity, object_homepostalcode,      
> object_homecountry, object_workstreet, object_workpob,      
> object_workcity, object_workpostalcode, object_workcountry, object_tz,
>       object_title, object_role, object_company, object_department,
   
>   object_logo, object_manager, object_notes, object_url,      
> object_pgppublickey, object_smimepublickey, object_uid, object_id)    
 
> VALUES ('Object', 'Hans', 'Depp', '', '', '', '', '', '', '', '', '',
>       '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '',
> '',       '', NULL, '', '', '', '', '',      
> '20150424183029.rPQk6iCuvsK5ptqa3fx6i
> Apr 24 20:30:29 luna HORDE: [turba] Serverfehler beim Hinzufügen der
> Daten. [pid 68351 on line 432 of
> "/usr/local/www/apache24/data/turba/lib/Driver/Sql.php"]
>  
>    I resolved to set the default value for owner_id through phpmyadmin
> and everything seems cool.
>
> However, if I did this to a productive system I would worry if this was
> the best - or at least a clean - way to do it.
> For instance, would it make more sense to make the change in a
> turba/migration/*.php file?
>  
>    Regards
>  
>      Sebastian
>     
>
>
>    2015-04-24 10:51 GMT+02:00 Sebastian Birnbach <birnbacs at gmail.com>:
>
>> Firstly, I removed all permissions in the admin console, with no
success.
>> Next, I added turba permissions again and assigned full access to every
>> logged-in user.
>> Added full access for guests.
>> Added full access for creator.
>> Added full access for single user.
>>  
>>        Added "Sources" permissions to turba permissions. Set the same
>> permissions as above.
>>         
>> None of these settings seemed to make a difference.
>>  
>>   Sebastian
>>
>>         2015-04-24 10:28 GMT+02:00 Jan Schneider <jan at horde.org>:
>>
>>> _Zitat von Sebastian Birnbach <birnbacs at gmail.com>:_
>>>
>>>> _Hmm, now everybody sees everything and everybody can make changes.
>>>> However, nobody can add a new contact._
>>>> _Got another nice solution for this?
>>>>  _
>>>> _Kind regards
>>>>  _
>>>> _  Sebastian_
>>>>
>>>>                _2015-04-24 8:48 GMT+02:00 Sebastian Birnbach
>>>> <birnbacs at gmail.com>:_
>>>>
>>>>> _Bingo, thanks again!
>>>>>  _
>>>>> _  Sebastian_
>>>>>
>>>>>                     _2015-04-24 8:38 GMT+02:00 Jan Schneider
>>>>> <jan at horde.org>:_
>>>>>
>>>>>> __Zitat von Sebastian Birnbach <birnbacs at gmail.com>:__
>>>>>>
>>>>>>> __Thanks again, Jan,
>>>>>>>  __
>>>>>>>                            __it appears that the now un-shared
>>>>>>> address book does not support user A create a contact and let user
>>>>>>> B see it. In fact it behaves like a set of private address books
>>>>>>> again, only without the option for sharing.
>>>>>>> Giving permissions for the turba application
>>>>>>> (turba->sources->shared address books) in the admin console to all
>>>>>>> users did not change things.
>>>>>>>
>>>>>>> Any ideas on that?
>>>>>>>  __
>>>>>>>                            __Kind regards
>>>>>>>  __
>>>>>>>                            __  Sebastian__
>>>>>>>
>>>>>>>
>>>>>>>                            __2015-04-22 9:21 GMT+02:00 Jan
>>>>>>> Schneider <jan at horde.org>:__
>>>>>>>
>>>>>>>> __Zitat von Sebastian Birnbach <birnbacs at gmail.com>:__
>>>>>>>>
>>>>>>>>> __Dear all,
>>>>>>>>>
>>>>>>>>> in my working environment everybody is supposed to use the same
>>>>>>>>> address
>>>>>>>>> book. I therefore created a special user the address book of who
>>>>>>>>> is
>>>>>>>>> accessible by any other user. Also, everybody can write into
>>>>>>>>> that special
>>>>>>>>> address book.
>>>>>>>>>
>>>>>>>>> Now I want to remove or disable all personal address books for
>>>>>>>>> everybody
>>>>>>>>> else so that for a search or new contact one needs not select an
>>>>>>>>> address
>>>>>>>>> book.
>>>>>>>>>
>>>>>>>>> Any straightforward way to do that?__
>>>>>>>>
>>>>>>>> __You should not use a shared address book then, but just a
>>>>>>>> simple global sql address book. If you don't have a backend
>>>>>>>> defined in backends.php that has 'use_shares' enabled, users
>>>>>>>> won't be able to create or use their own address books.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jan Schneider
>>>>>>>> The Horde Project
>>>>>>>> http://www.horde.org/
>>>>>>>> https://www.facebook.com/hordeproject
>>>>>>>>
>>>>>>>> --
>>>>>>>> turba mailing list
>>>>>>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>>>>>>> To unsubscribe, mail: turba-unsubscribe at lists.horde.org__
>>>>>>
>>>>>>
>>>>>>
>>>>>> __Remove the __owner attribute from the backend map.__
>>>>>>
>>>>>> -------------------------
>>>>>> __Jan Schneider
>>>>>> The Horde Project
>>>>>> http://www.horde.org/
>>>>>> https://www.facebook.com/hordeproject__
>>>
>>>
>>>
>>> _You may have incorrect permissions set._
>>>
>>> -------------------------
>>> _Jan Schneider
>>> The Horde Project
>>> http://www.horde.org/
>>> https://www.facebook.com/hordeproject_

If you don't use the default scheme for Turba, you cannot use the default
migrations. You have to adapt your scheme yourself.
-------------------------
Jan Schneider
The Horde Project
http://www.horde.org/
https://www.facebook.com/hordeproject


More information about the turba mailing list