[Kolab-devel] freebusy.php and pfb.php (Re: Alternative for dba_open?)

[Richard Bos]

Op vrijdag 31 maart 2006 23:42, schreef Richard Bos:
> However, with php5 is was not a problem for suse.  Or at least they could
> package around it.  It seems that this can be done for php4 as well, we
> have to wait if that will happen.  In the meantime Marcus was able to build
> the dba.so lib, and I was able to get use it succesfully :)
>
> A lot has happened and I don't think we need an alternative :)  (Just move
> to php5) ;)

The freebusy.php script seems to run now on suse, but when I review the output 
in the browser, some errors are reported.  Does anyone perhaps know why this 
might happen?  Do others see the correct output in the browser?  Here some 
information:

I use the following url:
https://<fqdn>/kolab/freebusy/freebusy.php?uid=test%40radoeka.nl

This results in (7 times):
Warning: Cannot modify header information - headers already sent by (output 
started at /usr/share/php/kolab/freebusy/freebusycache.class.php:342) 
in /srv/www/htdocs/kolab/freebusy/freebusy.php on line 112
(for the lines 112 -118 in freebusy.php).  That part of the script builds the 
header indeed:
// And finally send it out, ensuring it doesn't get cached along the way
header('Cache-Control: no-store, no-cache, must-revalidate');
header('Cache-Control: post-check=0, pre-check=0', false);
header('Pragma: no-cache');
header('Expires: Mon, 26 Jul 1997 05:00:00 GMT');
header('Last-Modified: ' . gmdate("D, d M Y H:i:s",$ts) . ' GMT');
header('Pragma: public');
header('Content-Transfer-Encoding: none');

At the bottom of the page the ical entry is displayed:
BEGIN:VCALENDAR VERSION:2.0 PRODID:-//proko2//freebusy 1.0//EN METHOD:PUBLISH 
BEGIN:VFREEBUSY ORGANIZER:MAILTO:test at adoeka.nl DTSTAMP:20060331T214229Z 
URL:http:/<fqdn>/kolab/freebusy/freebusy.php?uid= test%40radoeka.nl 
DTSTART:19691231T230000Z DTEND:19691231T230000Z COMMENT:This is a dummy 
vfreebusy that indicates an empty calendar 
FREEBUSY:19691231T230000Z/19691231T230000Z END:VFREEBUSY END:VCALENDAR

What could be a possible cause of those Warnings (where to start debugging)?
What see others running kolab from cvs?  If I run kolab 2.x the Warnings are 
not displayed.  There is just only the ical entry.



-- 
Richard Bos
Without a home the journey is endless