Freebusy Information blended

Gunnar Wrobel wrobel at pardus.de
Thu May 15 12:59:02 CEST 2008


Bernhard Reiter <bernhard at intevation.de> writes:

> On Thursday 08 May 2008 15:40, Saim Kim wrote:
>> Gunnar Wrobel schrieb:
>
>> >> I read the Freebusy draft from the CVS (rev 1.22). As far as I
>> >> understood my problem lies within the group calendar. The freebusy
>> >> generation was set to "readers" and therefore the partial freebusy
>> >> information of the group calendar was added to the freebusy generation
>> >> for every user with read permission set -so almost everybody. I changed
>> >> the freebusy generation to "nobody" and when I check under cyradm the
>> >> "incidences-for:" tag is set correctly to "nobody". Is there a way to
>> >> set this directly?
>> >
>> > You can set these values via Horde. Maybe also via Kontact, I don't
>> > know if the extended free busy stuff is already implemented there.
>
> Kontact can set these parameters for ages (it is unrelated to the 
> extended-freebusy usage).

Ah, okay. I mixed that up because I implemented them together in
Horde. Sorry for the misinformation.

Cheers,

Gunnar

>
> Note that I think a new trigger for each folder needs to happen
> to see an effect.
>
>> Ok, I found the interface under the following URL:
>> https://kolab.mydomain.org/fbview. I also checked the settings for the
>> freebusy generation
>>
>> > Or do you refer to the default value that should be changed? Then you
>> > should probably comment on Bernhards mail concerning the free/busy
>> > draft. Maybe we should use a different default value and should
>> > specify this in the draft.
>
> Again: This is mixing up things. The extended-Freebusy is unrelated
> to the concept of for whom the entries should be relevent ("incidences-for").
>
>> Not quite sure which default value you mean.
>
> I believe the default value to be "admins".
> Should be in the architecture draft or the format.
>
>> >> Unfortunatly, this hasn't solved the problem, yet.
>> >
>> > Meaning the setting had no effect?
>>
>> Yes, the setting for the "freebusy relevance" did not have an influence
>> on the event blending of the other users.
>> Is there a way to flush the freebusy cache?
>
> A trigger on the right folder should do the trick, if it does not, file a 
> report!
>
> Bernhard
>
>
>
> -- 
> Managing Director - Owner: www.intevation.net       (Free Software Company)
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
> Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
> Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~




More information about the users mailing list