[Tickets #6034] Re: users' kolab addressbook entries not editable

bugs at horde.org bugs at horde.org
Wed Dec 26 03:17:49 UTC 2007


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

Ticket URL: http://bugs.horde.org/ticket/?id=6034
-----------------------------------------------------------------------
 Ticket             | 6034
 Updated By         | m.gabriel at das-netzwerkteam.de
 Summary            | users' kolab addressbook entries not editable
 Queue              | Kolab
 Type               | Bug
 State              | Unconfirmed
 Priority           | 3. High
 Owners             | 
+New Attachment     | Object.php.patch
-----------------------------------------------------------------------


m.gabriel at das-netzwerkteam.de (2007-12-25 22:17) wrote:

did a bit of debugging...

the problem is that with kolab the source of kolab's default user contact
folder is equal to the user's email adress. other non-default contact
folders have the name of the cyrus path, e.g. INBOX/Contacts_private.

So address book entries in non-default contact folders are modifiable...
but not so the kolab user default contact folder...

the issue originates in turba/lib/ListView.php and goes further down into
turba/lib/Object.php. Everything rendered in ListView.php is passed on to
further pages (view.php, edit.php, etc. by
Variables::getDefaultVariables())

when rendering a table row (row.inc) in ListView.php, the method
ob->getSource() (row.inc) returns INBOX/Contacts for the kolab user default
contact folder, but should return user at domain.

looking closely at the Turba_Driver::getSource() method in
turba/lib/Object.php:

<quoting>
function getSource() {
  return $this->driver->getName()
}
</quoting>

this should call the Turba_Driver::getName() method in
turba/lib/Driver.php, which then - in a proper object oriented environment
- should return 

function getName() {
  return $this->driver->name;
}

but it does not... or it does, but we have two different values for the
same expression ($this->driver->name).

anyway, find a patch attached, that works well with kolab, not sure about
other backends...






More information about the bugs mailing list