On Sun, Oct 24, 2010 at 03:05:32PM +0200, Evgeni Golov wrote: > Hi, > > there are two ways of handling this. > > Either you set > $conf['debug_level'] = E_ALL & ~E_NOTICE & ~E_DEPRECATED; > in /etc/horde/horde3/conf.php, which will disable all Deprecation > warnings (warnings meant for developers shouldn't be shown to users > anyways).
Not effective. Less warnings but still fails. > Or you patch the source not to use the deprecated &new. > I did so by running > sed -i -e 's#=.*&[ ]*new#= new#' `grep -rl "=.*&[ ]*new" .` > in the source tree. I have no Horde here to test, so the attached patch > that was the result of the above sed-orgy may burn your server, kill > your kittens and eat your sushi - use with caution and have backups :) More effective, looks promising. Presumably the horde framework apps will have similar problems? -- Phil Reynolds mail: phil-deb...@tinsleyviaduct.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
