Freebusy genearation in kolab+horde+toltec

Hi everybody, i'm trying to put together a setup of Horde
alpha + Kolab
storage + toltec plugin for integration with outlook.
To achieve the integration between kronolith and toltec, i
did change the
encoding kronolith uses to store on imap folder to base64
(it was
quoted-printable). It worked, even with shared calendars.
My problem now is to generate the free/busy info. I get an
empty file.
Looking arround, putting some prints in fb.php and
lib/FreeBusy.php and
got this error from PEAR: Share
"user/pepe/Calendar" does not exist. (this
is a calendar and it exist). I understand that with Kolab
patches to
Kolab, shares are no longer stored on mysql, so, where are
they now?

Is this feature working? I found this email saying no, but
it's old.
http://www.intevation.de/pipermail/kolab
-users/2006-December/005728.html

I will appreciate any hint on this.

Regards.

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

"Ariel Wainer" <arielxtech.com.ar> writes:

> Hi everybody, i'm trying to put together a setup of
Horde alpha + Kolab
> storage + toltec plugin for integration with outlook.
> To achieve the integration between kronolith and
toltec, i did change the
> encoding kronolith uses to store on imap folder to
base64 (it was
> quoted-printable). It worked, even with shared
calendars.
> My problem now is to generate the free/busy info. I get
an empty file.
> Looking arround, putting some prints in fb.php and
lib/FreeBusy.php and
> got this error from PEAR: Share
"user/pepe/Calendar" does not exist. (this
> is a calendar and it exist). I understand that with
Kolab patches to
> Kolab, shares are no longer stored on mysql, so, where
are they now?

Horde shares are mapped to IMAP folders and a mysql db is
indeed not
needed anymore.

>
> Is this feature working? I found this email saying no,
but it's old.
> http://www.intevation.de/pipermail/kolab
-users/2006-December/005728.html

Free/Busy? Yes, that feature should be working. At least on
a
Kolab-Server-2.2-beta2 system. You don't specify which
versions and
patches you are using so I don't know if it will work in
your setup.

Cheers,

Gunnar

>
> I will appreciate any hint on this.
>
> Regards.
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

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

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

> Free/Busy? Yes, that feature should be working. At
least on a
> Kolab-Server-2.2-beta2 system. You don't specify which
versions and
> patches you are using so I don't know if it will work
in your setup.
>

Sorry, did not copy the list in my answer:

Thanks for the quick answer, the kolab-cyrus-imapd 2.2.13-2
(debian etch
package) and the patches are:

HK-GW-framework_3.2_ALPHA-Fix_annotation_use.patch
HK-GW-framework_3.2_ALPHA-Fix_Prefs_for_Ingo.patch
HK-GW-framework_3.2_ALPHA-Fix_the_share_params.patch
HK-GW-framework_3.2_ALPHA-Share_caching.patch
HK-GW-kronolith_2.2-Fix_create_new_event.patch
HK-GW-kronolith_2.2-Fix_share_right_editing.patch
HK-GW-mnemo_2.2_ALPHA-Edit_share_rights.patch
HK-GW-nag_2.2_ALPHA-Fix_share_right_editing.patch
HK-GW-turba_2.2-Changes_after_ALPHA.patch
HK-GW-turba_2.2-Fix_address_book_deletion_1.patch
HK-GW-turba_2.2-Fix_editing_contacts.patch
HK-GW-turba_2.2-Fix_notice_on_addressbook_creation.patch
HK-GW-turba_2.2-Fix_share_id_change.patch
HK-GW-turba_2.2-Ldap_read_only_fix.patch
HK-UV-kronolith_2.2-Fix_list_events.patch






_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

"Ariel Wainer" <arielxtech.com.ar> writes:

>> Free/Busy? Yes, that feature should be working. At
least on a
>> Kolab-Server-2.2-beta2 system. You don't specify
which versions and
>> patches you are using so I don't know if it will
work in your setup.
>>
>
> Sorry, did not copy the list in my answer:
>
> Thanks for the quick answer, the kolab-cyrus-imapd
2.2.13-2 (debian etch
> package) and the patches are:

Oh, looks like you are using Kolab2/Debian. I admit I don't
know
anything about their packages and can't tell you if
free/busy is
supposed to work on the native debian version.

For support/request concerning the Kolab2/Debian packages I
suggest
directing these at their mailing list:

http://
alioth.debian.org/mail/?group_id=30845

Their project page is here:

http://pkg-kolab.
alioth.debian.org/

>
> HK-GW-framework_3.2_ALPHA-Fix_annotation_use.patch
> HK-GW-framework_3.2_ALPHA-Fix_Prefs_for_Ingo.patch
> HK-GW-framework_3.2_ALPHA-Fix_the_share_params.patch
> HK-GW-framework_3.2_ALPHA-Share_caching.patch
> HK-GW-kronolith_2.2-Fix_create_new_event.patch
> HK-GW-kronolith_2.2-Fix_share_right_editing.patch
> HK-GW-mnemo_2.2_ALPHA-Edit_share_rights.patch
> HK-GW-nag_2.2_ALPHA-Fix_share_right_editing.patch
> HK-GW-turba_2.2-Changes_after_ALPHA.patch
> HK-GW-turba_2.2-Fix_address_book_deletion_1.patch
> HK-GW-turba_2.2-Fix_editing_contacts.patch
>
HK-GW-turba_2.2-Fix_notice_on_addressbook_creation.patch
> HK-GW-turba_2.2-Fix_share_id_change.patch
> HK-GW-turba_2.2-Ldap_read_only_fix.patch
> HK-UV-kronolith_2.2-Fix_list_events.patch

Looks okay.

Cheers,

Gunnar


>
>
>
>
>
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

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

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On Tuesday 23 October 2007 18:16, Gunnar Wrobel wrote:
> Oh, looks like you are using Kolab2/Debian. I admit I
don't know
> anything about their packages and can't tell you if
free/busy is
> supposed to work on the native debian version.

I do not know either if Kolab Server/Debian is in a good
state,
so asking them is a good idea.

If you want to debug this further yourself, this might
help:
http://wiki.kolab.org/index.php/Kolab2_
Server_Troubleshooting_-_Free/Busy

> For support/request concerning the Kolab2/Debian
packages I suggest
> directing these at their mailing list:
>
> http://
alioth.debian.org/mail/?group_id=30845
>
> Their project page is here:
>
> http://pkg-kolab.
alioth.debian.org/

-- 
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-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users