[Tickets #9003] Re: Cannot modify header information - headers already sent

bugs at horde.org bugs at horde.org
Wed Jul 28 19:45:22 UTC 2010


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9003
------------------------------------------------------------------------------
  Ticket             | 9003
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Cannot modify header information - headers already sent
  Queue              | Horde Groupware Webmail Edition
  Version            | 1.2.6
  Type               | Bug
  State              | Not A Bug
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2010-07-28 15:45) wrote:

> that's the issue: as far as I understood the pear is moving from  
> php4 to php5 (pear/Log i.e.: There is unfortunately no way to  
> support both PHP4 and PHP5 in the same code base when running under  
> E_ALL.

Well, that's not technically true, but that's another story.

Because
> it appears that the majority of Log package users have moved to  
> PHP5, the Log package now targets that audience."
>
> so the horde way to not support newer php5 but sticking with php4 is bad.

I didn't say we don't support php5.  I said Horde *3* is compatible  
with PHP 4. All new development work is being done on Horde 4, which  
is PHP 5 native.

> So horde is one with not supporting the current php5 releases so I  
> stay with it: it's a bug.

I fail to see how a version of Horde that is designed to work with PHP  
4 spitting out warning messages when used with PHP 5 is a bug. Not to  
mention that these error messages shouldn't be making it to the  
browser window on a production system anyway...

To summarize again: Horde 4 is PHP 5 native. Horde 3 works perfectly  
fine with PHP 5 as long as the deprecated warnings don't make it to  
the browser. (Again, see jan's previous comments).






More information about the bugs mailing list