[pkg-horde] Bug#487799: Bug#487799: Bug#487799: horde3: Horde fails to configure after standard install

[Nikolaus Rath]

Gregory Colpart <reg at evolix.fr> writes:
> Hello,
>
> On Wed, Jun 25, 2008 at 01:38:34PM +0200, Nikolaus Rath wrote:
>> >
>> > This bug is already reported in #452351
>> > (http://bugs.debian.org/452351) and corrected in lenny/unstable.
>> > The workaround is also in wiki.debian.org/Horde :
>> 
>> No, as I explicitly said in my bug report I already applied this fix.
>> You can also see from the screenshots that I attached that I get very
>> different error messages.
>
> Oops, sorry, I didn't open your screenshots. Then I see that your
> errors are in sidebar when Horde isn't yet configured.
>
> => You must configured Horde *before* installing other
> applications. I think I will desactive all applications by
> default in registry.php to avoid this errors.

Well, I would really like to do that, but I *couldn't*. All I ever saw
(except for the menu icons) is error messages. So I can click on
"Administration" -> "Setup", but as soon as I select an application I
get only error messages, mostly about trying to access nonexisting
hash keys.


Luckily enough, I was able to trace down the cause now. After I added
$conf['log']['enabled'] = false to conf.php I was at least able to
configure horde. After logging out and restarting the browser, the
remaining error messages disappeared as well.


Horde seems to be a great application, thanks for packaging it. Yet I
think that the installation process could be improved. Is it really
not possible to get such critical bugfixes into etch? It seems to me
that expecting the user to fix two major bugs before he has even seen
anything from the application is quite unfortunate.

Best,

   -Nikolaus

-- 
 Nikolaus at rath.org | College Ring 6, 28759 Bremen, Germany
 Class of 2008 - Physics | Jacobs University Bremen

 »My opinions may have changed, but not the fact that I am right.«