<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>LDAP List of Contacts fails with missing contact</title> 
  <pubDate>Fri, 10 Apr 2026 03:14:03 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/13941</link> 
  <atom:link rel="self" type="application/rss+xml" title="LDAP List of Contacts fails with missing contact" href="https://bugs.horde.org/ticket/13941/rss" /> 
  <description>LDAP List of Contacts fails with missing contact</description> 
 
   
   
  <item> 
   <title>I&#039;m using LDAP as backend for turba
Creating a list of cont</title> 
   <description>I&#039;m using LDAP as backend for turba
Creating a list of contacts leads in a link of  contact-dns in the contact list object.

If the origin contact is deleted, the dn in the contact list is missing.
Browsing the list leads in an exception. The whole list is not useable

I discovered that the Kolab driver makes use of the driver option &quot;removeMissing&quot;
In my case, i think a similar procedure would fix the problem.

But where should this option be set?
Should I implement an objectOptions field in config/backends.php to remove missing listmembers?

Should this option be a bool value?
listMembers function of Turba_Object_Group checks only !empty($this-&gt;_options[&#039;removeMissing&#039;]) an not set to true


bug priority: very low
but: If the further proceeding is clear, I would create a patch to fix
</description> 
   <pubDate>Tue, 07 Apr 2015 19:56:34 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13941#t87915</link> 
  </item> 
   
  <item> 
   <title>The actual bug is that there shouldn&#039;t be an exception leadi</title> 
   <description>The actual bug is that there shouldn&#039;t be an exception leading to a fatal error. Can you please provide the full error message and backtrace?
But to answer your original question: it&#039;s sufficient to copy the $_objectOptions setting from the Kolab driver to the LDAP driver.</description> 
   <pubDate>Thu, 09 Apr 2015 15:06:22 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13941#t87924</link> 
  </item> 
   
  <item> 
   <title>&gt; The actual bug is that there shouldn&#039;t be an exception lea</title> 
   <description>&gt; The actual bug is that there shouldn&#039;t be an exception leading to a 
&gt; fatal error. Can you please provide the full error message and 
&gt; backtrace?

In Turba_Driver_Ldap function _read() is called with an none existing dn.
@ldap_read returns no (false) result and ldap_error is &quot;No such object&quot;
 -&gt; throw new Turba_Exception(sprintf(_(&quot;Read failed: (%s) %s&quot;), ldap_errno($this-&gt;_ds), ldap_error($this-&gt;_ds)))


Turba_Driver&#039;s getObjects() has no exception handling and
Turba_Object_Group&#039;s listMembers() catches only Horde_Exception_NotFound


This results in a red notification box: &quot;Failed to browse list&quot; and no existing list members are displayed

quick fix:
catching a Turba_Exception also (in listMembers) leads in a
&quot;There is 1 contact in this list that is not viewable to you&quot;
witch would be correct

But: Maybe the Turba_Driver_Ldap should throw a Horde_Exception_NotFound in case of &quot;No such object&quot; error

&gt; But to answer your original question: it&#039;s sufficient to copy the 
&gt; $_objectOptions setting from the Kolab driver to the LDAP driver.
This would be nice to have in one of the next turba releases</description> 
   <pubDate>Thu, 09 Apr 2015 18:27:00 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13941#t87926</link> 
  </item> 
   
  <item> 
   <title>Maybe ticket #13197 is related</title> 
   <description>Maybe ticket #13197 is related</description> 
   <pubDate>Thu, 09 Apr 2015 18:31:55 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13941#t87927</link> 
  </item> 
   
  <item> 
   <title>&gt; Maybe ticket #13197 is related

I agree that it is relat</title> 
   <description>&gt; Maybe ticket #13197 is related

I agree that it is related to the bug mentioned above.</description> 
   <pubDate>Mon, 13 Apr 2015 12:10:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13941#t87945</link> 
  </item> 
   
  <item> 
   <title>This should already be fixed in Git since Turba_Driver_Ldap:</title> 
   <description>This should already be fixed in Git since Turba_Driver_Ldap::_read() now correctly throws Horde_Exception_NotFound.</description> 
   <pubDate>Wed, 15 Apr 2015 15:26:36 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/13941#t87970</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
