<?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>No icons are being displayed in chora due to bug in MIME_Viewer::getIcon</title> 
  <pubDate>Thu, 09 Apr 2026 22:18:03 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/28</link> 
  <atom:link rel="self" type="application/rss+xml" title="No icons are being displayed in chora due to bug in MIME_Viewer::getIcon" href="https://bugs.horde.org/ticket/28/rss" /> 
  <description>No icons are being displayed in chora due to bug in MIME_Viewer::getIcon</description> 
 
   
   
  <item> 
   <title>I have the global horde $mime_drivers array setup and config</title> 
   <description>I have the global horde $mime_drivers array setup and configured with icons, and nothing in the chora mime_drivers.php.. 

Vieweing of a .c file calls the appropriate mime viewer (enscript), but in the directory view there are no icons for Chora.. I&#039;ve tracked down the problem to line 394 of MIME/Viewer.php where the _getIcon function returns null because $mime_drivers[&#039;chora&#039;] is not set.. Shouldn&#039;t the getIcon function also check for the &#039;horde&#039; application if &#039;chora&#039; does not have any settings? It looks like code is in there to do that, but it is not working due to $ob being set to null for the compare in getIcon.</description> 
   <pubDate>Tue, 23 Mar 2004 20:32:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/28#t121</link> 
  </item> 
   
  <item> 
   <title></title> 
   <description></description> 
   <pubDate>Tue, 23 Mar 2004 20:35:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/28#t122</link> 
  </item> 
   
  <item> 
   <title>Fixed in CVS already, but thanks for your patch!</title> 
   <description>Fixed in CVS already, but thanks for your patch!</description> 
   <pubDate>Wed, 24 Mar 2004 22:50:24 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/28#t123</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
