[Kolab-devel] Horde temporary dir in kolab 2.2 beta3

[Gelpi Andrea]

Gunnar Wrobel wrote:
> Gelpi Andrea <liste at gelpi.it> writes:
> 
>> In /kolab/var/kolab/www/horde/config/conf.php this 2 lines point to non existent 
>> directory.
>>
>>
>> $conf['tmpdir'] = dirname(__FILE__) . '/../../../tmp/horde';
>> $conf['vfs']['params']['vfsroot'] = dirname(__FILE__) . '/../../../tmp/horde';
>>
>>
>> In my new installation they point to:
>>
>> /kolab/lib/php/Horde/../../../tmp/horde
>>
>> that does not exist.
>>
>> I add:
>>
>> mkdir -p /kolab/tmp/horde
>> chwon -R kolab.kolab /kolab/tmp
>>
> 
> Seems incorrect since
> 
> dirname(__FILE__)
> 
> in /kolab/var/kolab/www/horde/config/conf.php should evaluate to
> 
> /kolab/var/kolab/www/horde/config
> 
> and thus $conf['tmpdir'] should point to 
> 
> /kolab/var/kolab/www/horde/config/../../../tmp/horde
> 
> => 
> 
> /kolab/var/kolab/tmp/horde
> 
> Where do you get the "/kolab/lib/php/Horde" base directory?
> 
> Cheers,
> 
> Gunnar
> 

I login as user manager and I looked at horde configuration file.
I know (you told me yesterday) that this file is not complete due to kolab.php.
But in kolab.php there are no overrides for $conf['tmpdir'].
So I suppose what I was seeing was correct.

Today in the afternoon I create a phpinfo page and from there I found what you 
have written before in this note.

I think that having the opportunity to view and also modify the configuration 
files via manager user could be dangerous or confusing.

Don't you think that a warning in 1st.README could be great, do you?

-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************