On 4/28/2011 6:26 AM, Martin Muskulus wrote:
Hi,
[27-Apr-2011 19:15:25] PHP Deprecated: Assigning the return value of new by reference is deprecated in /usr/share/php/MDB2.php on line 2647
This is an error message from the PEAR MDB2 package not from Roundcube itself.
Roundcube seems to use PEAR MDB2 package for database connectivity. The current stable release of MDB2 uses assignments by reference (=& new ). There is a newer beta of the MDB2 package available where changelog says dropped php4 support and php5.3 fixes. It can be installed by shell command "pear upgrade MDB2-beta" or you can grab it from http://pear.php.net/package/MDB2/download/
This didn't fix the redirect problem, but it does seem to have squelched the log errors.
Back to the original problem... My lighttpd, RC 0.3.1, PHP5, sqlite packages are part of stock Debian 6.0 AFAIK. I've just posted a message on debian-user about this RC problem; hoping to hear something soon.
Per one of the suggestions on the RC forum, I went to disable Suhosin in PHP, but the Debian PHP5 has Suhosin compiled into the binary, so I can't disable it. If it's possible I've not discovered how. It shouldn't matter as both packages are standard Debian 6 packages, and should thus have been tested to work together.
Multiple people on the forum have reported the same login redirection problem, but only with 0.4.x and 0.5.x IIRC. In each case the problem was solved by different means. One guy fixed it by replacing index.php or main.inc.php as it was apparently missed during an upgrade. My "upgrade" was from 0.3.1 to 0.3.1 so this isn't an option. Another guy fixed it by disabling Suhosin. This tells me there are multiple causes of the login redirection problem, and no definitive answer. :(
This is getting really frustrating. I removed and reinstalled the Debian RC package, same for all the PHP5 packages, and that didn't help. I was using RC 0.3.1 from Lenny backports before the Squeeze upgrade, which also contains RC 0.3.1. Thus, it shouldn't be a problem with my config files, which have not changed.
This issue only seems to occur after upgrades. It would be nice if there were some documentation regarding this problem, or simply some log entries telling me where to look.