<?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>Horde_Image_gd throws errors with the wrong message</title> 
  <pubDate>Fri, 10 Apr 2026 09:50:13 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/8155</link> 
  <atom:link rel="self" type="application/rss+xml" title="Horde_Image_gd throws errors with the wrong message" href="https://bugs.horde.org/ticket/8155/rss" /> 
  <description>Horde_Image_gd throws errors with the wrong message</description> 
 
   
   
  <item> 
   <title>The PEAR::raiseError call is causing the following error mes</title> 
   <description>The PEAR::raiseError call is causing the following error message to appear on my system Mac OSX.



imageCreateFromString: Non-static method PEAR::raiseError() should not be called statically, assuming $this from incompatible context



This is a problem because it is the wrong error message, generated from including PEAR.php at E_STRICT debug level.  Suggest changing the following lines like so:



BEFORE



require_once &#039;PEAR.php&#039;;

$result = PEAR::raiseError($function . &#039;: &#039; . $php_errormsg);



AFTER



$errormsg = $php_errormsg;

require_once &#039;PEAR.php&#039;;

$result = PEAR::raiseError($function . &#039;: &#039; . $errormsg);

</description> 
   <pubDate>Mon, 06 Apr 2009 15:13:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8155#t53558</link> 
  </item> 
   
  <item> 
   <title>I understand the issue, but I don&#039;t see where PEAR is being </title> 
   <description>I understand the issue, but I don&#039;t see where PEAR is being included with E_STRICT explicitly set. Where is this happening?</description> 
   <pubDate>Mon, 06 Apr 2009 15:54:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8155#t53559</link> 
  </item> 
   
  <item> 
   <title>Ok. You can disregard that last question. It seems that PHP </title> 
   <description>Ok. You can disregard that last question. It seems that PHP will track ANY error into $php_errormsg, regardless of if that error would have been thrown under the current error_reporting level.</description> 
   <pubDate>Mon, 06 Apr 2009 16:31:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8155#t53560</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/framework/Image/Image/gd.php?rt=horde&amp;r1=1.84&amp;r2=1.85&amp;ty=u</description> 
   <pubDate>Mon, 06 Apr 2009 16:35:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8155#t53561</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/framework/Image/Image/gd.php?rt=horde&amp;r1=1.48.10.21&amp;r2=1.48.10.22&amp;ty=u</description> 
   <pubDate>Mon, 06 Apr 2009 16:36:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8155#t53562</link> 
  </item> 
   
  <item> 
   <title>Fixed, thanks for the report!</title> 
   <description>Fixed, thanks for the report!</description> 
   <pubDate>Mon, 06 Apr 2009 16:37:20 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/8155#t53563</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
