Fri, 10 Apr 2026 09:50:13 +0000 https://bugs.horde.org/ticket/9003 Cannot modify header information - headers already sent Hi, I chose "Horde Groupware Webmail Edtion 1.2.5 Final" as "Horde Groupware Webmail Edtion 1.2.6 Final" is not yet in the list. The issue is however in 1.2.6. After installing Horde I get the following message when accessing index.php: Warning: Cannot modify header information - headers already sent by (output started at /path/horde-webmail-1.2.6/pear/php/Log.php:169) in /path/horde-webmail-1.2.6/index.php on line 97 Apache 2.2.14 Ubuntu server 10.04 PHP 5.3.2 Any idea what this could be? Thanks, Chris. Mon, 03 May 2010 15:00:50 +0000 https://bugs.horde.org/ticket/9003#t58702 There is no code in this line that would produce any output. Are you that this is not a follow-up error of some other, earlier error message? Mon, 03 May 2010 15:24:03 +0000 https://bugs.horde.org/ticket/9003#t58703 Hi Jan, How can I find this out? The complete output of the page is: Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/pear/php/Log.php on line 169 Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/lib/Horde/Notification.php on line 64 Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/lib/Horde/Perms.php on line 455 Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/lib/Horde/Perms.php on line 462 Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/lib/Horde/Perms/sql.php on line 83 Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/lib/Horde/Perms/sql.php on line 116 Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/lib/Horde/Perms/sql.php on line 153 Deprecated: Assigning the return value of new by reference is deprecated in /path/horde-webmail-1.2.6/lib/Horde/Prefs.php on line 847 Warning: Cannot modify header information - headers already sent by (output started at /path/horde-webmail-1.2.6/pear/php/Log.php:169) in /path/horde-webmail-1.2.6/index.php on line 97 There are no error messages in the apache logs. Please let me know how I can help debug. Regards, Chris. Mon, 03 May 2010 15:40:19 +0000 https://bugs.horde.org/ticket/9003#t58704 Configure PHP or Horde to not include E_DEPRECATED in the error level. Please use the mailing list to ask for support. http://www.horde.org/mail/ contains a list of all available mailing lists. Mon, 03 May 2010 15:52:09 +0000 https://bugs.horde.org/ticket/9003#t58705 > Configure PHP or Horde to not include E_DEPRECATED in the error level. > > Please use the mailing list to ask for support. > > http://www.horde.org/mail/ contains a list of all available mailing lists. I think it is a bug - horde ist not well working with the latest php version 5.3 which is shipped with Ubuntu 10.04 (and other distros as well). Any clue when the issue (I' refering to the "warning" line, not the "deprecated" lines) "Warning: Cannot modify header information - headers already sent by " is fixed with horde? Wed, 28 Jul 2010 19:04:29 +0000 https://bugs.horde.org/ticket/9003#t59494 > I think it is a bug - horde ist not well working with the latest php > version 5.3 which is shipped with Ubuntu 10.04 (and other distros as > well). 1) Horde 3 must maintain backwards compatibility with PHP 4. Horde 4 will require PHP 5.2 or later. 2) The "warning" line you refer to is NOT a horde issue. It is a side effect of the deprecated error lines being output to the browser. See Jan's earlier response. 3) The lines actually causing the problem are not even Horde code, they are in PEAR libraries. Please use the mailing list for further questions or support. Wed, 28 Jul 2010 19:15:58 +0000 https://bugs.horde.org/ticket/9003#t59495 > 3) The lines actually causing the problem are not even Horde code, > they are in PEAR libraries. This, of course, should read "Some of the lines". Wed, 28 Jul 2010 19:17:21 +0000 https://bugs.horde.org/ticket/9003#t59496 Hi >> I think it is a bug - horde ist not well working with the latest php >> version 5.3 which is shipped with Ubuntu 10.04 (and other distros as >> well). > > 1) Horde 3 must maintain backwards compatibility with PHP 4. Horde 4 > will require PHP 5.2 or later. 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. 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. So horde is one with not supporting the current php5 releases so I stay with it: it's a bug. Wed, 28 Jul 2010 19:37:28 +0000 https://bugs.horde.org/ticket/9003#t59498 > 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). Wed, 28 Jul 2010 19:45:21 +0000 https://bugs.horde.org/ticket/9003#t59499