<?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>Accessing /dimp/compose.php generates &#039;headers already sent in Unknown on line 0&#039;</title> 
  <pubDate>Fri, 10 Apr 2026 13:16:50 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/9048</link> 
  <atom:link rel="self" type="application/rss+xml" title="Accessing /dimp/compose.php generates &#039;headers already sent in Unknown on line 0&#039;" href="https://bugs.horde.org/ticket/9048/rss" /> 
  <description>Accessing /dimp/compose.php generates &#039;headers already sent in Unknown on line 0&#039;</description> 
 
   
   
  <item> 
   <title>It seems this is a problem with output buffering. ob_start i</title> 
   <description>It seems this is a problem with output buffering. ob_start in dimp/lib/Views/Compose.php opens a new output buffer on the stack but then calls ob_clean instead of ob_end_clean to destroy the temporary buffer. From the ob_start manual:

Output buffers are stackable, that is, you may call ob_start() while another ob_start() is active. Just make sure that you call ob_end_flush()  the appropriate number of times. If multiple output callback functions are active, output is being filtered sequentially through each of them in nesting order.</description> 
   <pubDate>Wed, 19 May 2010 14:52:18 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9048#t58907</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

Bug: 9048
Su</title> 
   <description>Changes have been made in CVS for this ticket:

Bug: 9048
Submitted by: Valentin.Vidic@CARNet.hr
Remove buffer after done using it.
http://cvs.horde.org/diff.php/dimp/lib/Views/Compose.php?rt=horde&amp;r1=1.20.2.13&amp;r2=1.20.2.14&amp;ty=u</description> 
   <pubDate>Wed, 19 May 2010 17:01:03 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9048#t58909</link> 
  </item> 
   
  <item> 
   <title>This doesn&#039;t technically solve your issue - there is still a</title> 
   <description>This doesn&#039;t technically solve your issue - there is still a problem somewhere in your output chain.  This solution just happens to mask the error message.

However, it is proper to remove this buffer when finished using it for the limited purpose for which it is needed, so it has been fixed.</description> 
   <pubDate>Wed, 19 May 2010 17:01:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/9048#t58910</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
