<?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>php include_path hard coded, fails to load distribution PEAR packages</title> 
  <pubDate>Fri, 10 Apr 2026 09:20:56 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8256</link> 
  <atom:link rel="self" type="application/rss+xml" title="php include_path hard coded, fails to load distribution PEAR packages" href="https://bugs.horde.org/ticket/8256/rss" /> 
  <description>php include_path hard coded, fails to load distribution PEAR packages</description> 
 
   
   
  <item> 
   <title>in horde-webmail-1.2.3-final&#039;s lib/core.php there is a hard </title> 
   <description>in horde-webmail-1.2.3-final&#039;s lib/core.php there is a hard coded php include_path set. as there are many PEAR packages that are not bundled in horde the user needs to include his/her distribution&#039;s PEAR packages, as well (for example Net/IMAP). 



When non-bundled PEAR packages are missing horde behaves really weird and people who have set their site php.ini up properly keep searching for their mistake (as a missing Net/IMAP package was really hard to debug on my site, no php-errors wheresoever). 



There should be at least in hint in docs/INSTALL.</description> 
   <pubDate>Fri, 08 May 2009 07:52:01 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8256#t54054</link> 
  </item> 
   
  <item> 
   <title>Having PEAR bundled with the groupware is to *not* having us</title> 
   <description>Having PEAR bundled with the groupware is to *not* having users fiddle with the PEAR installation. If there are any PEAR packages missing in the bundle that are required by some parts of Horde Groupware, open a new bug for those.

The data path being hardcoded is already covered by a different ticket.</description> 
   <pubDate>Tue, 12 May 2009 14:22:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8256#t54092</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
