Odd that your system wouldn't have that timezone.
Can you post the output of:
print_r( DateTimeZone::listIdentifiers() );
If Europe/Berlin is indeed in there, can you send me the calendar you're trying to use?
Perhaps there's something odd in there.
Thanks!
Evert
> --
> You received this message because you are subscribed to the Google Groups "SabreDAV Discussion" group.
> To post to this group, send email to sabredav...@googlegroups.com.
> To unsubscribe from this group, send email to sabredav-discu...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sabredav-discuss?hl=en.
>
On Feb 20, 2012, at 9:00 PM, kanka wrote:
> Hi,
>
> I got bitten with this one too, the only difference being for the
> Europe/Paris Timezone.
I don't think your issue is the same. In your example the X-LIC-Location should be parsed.
One question:
Can you set:
$server->debugExceptions = true;
and send me the output of that HTTP/1.1 500 again? This tells me exactly where the error is.
Thanks!
Evert
> Ah, I just got an answer from Marten, the developper of caldav-sync
> (the android app). Here it is:
>
> this looks like a known bug in SabreDAV. Please see the known issues
> in my
> wiki for details: http://dmfs.org/wiki/index.php?title=OwnCloud
> SabreDAV crashes on a calendar-query when there are events that
> contain a
> time zone that it doesn't recognize.
> I'm not sure if this is fixed in SabreDAV yet, but you could try to
> upgrade SabreDAV.
In version 1.6.0 this is fully fixed.. SabreDAV will default to the system timezone if it doesn't recognize the timezone.
But my plan is still to try a 'best effort' for finding out the correct timezone id.
I'm pretty sure the bug you found is not fixed in 1.5.7, so I'll definitely correct this.
Thanks for the info!
Evert
https://github.com/evert/SabreDAV/zipball/1.5
> I'm running into the same problem. I've applied your patch linked
> above, but am still getting an error on calendar-query. I've verified
> that the time zone it's complaining about (America/Chicago) does exist
> on my server. Here's what I can see in my log:
Not quite the same error. Judging from your error, it appears that the name of that timezone contains literal quotes.
Can you please post the calendar object that triggers this?
You should be able to find it by doing a database search on the string "America/Chicago" (including the quotes!)
Would love to get a hint to find out which client software may have produced this.
Evert
> Thanks for the prompt reply. I imported the schedule for my local team
> (Chicago Blackhawks) into my ownCloud 3.0 install of SabreDAV. You can
> get the same .ics from here:
>
> http://blackhawks.nhl.com/v2/ext/iCal-Files/Blackhawks-Schedule-2011-12.ics
>
> I used eM Client to import it, and it can be viewed fine from eM
> Client and ownCloud. The error comes in when I try to sync the
> calendar to my android phone using CalDAV-sync from dmfs.org.
I created a small script to test this ics:
<?php
include 'lib/Sabre/autoload.php';
$vObject = Sabre_VObject_Reader::read(file_get_contents('test.ics'));
foreach($vObject->VEVENT as $event) {
echo $event->DTSTART->getDateTime()->format(DATE_ATOM), " ", $event->summary,"\n";
}
?>
And it comes out correctly. My guess is that emClient messes with the data.
I really need to see exactly how to the event gets stored in the database..
Evert
> Hi Evert,
>
> You're absolutely correct. eM Client appears to be storing it with the
> quotes when I import the ics through there. I imported the same file
> through ownCloud and it seems to be working just fine now. Below is an
> example of an event as it exists in the db after import from eM
> Client.
Ok, this does seem like a bug.. I'll look into this soon.
Evert
On Mar 30, 2012, at 3:41 AM, bill wrote:
> Hi Evert,
>
> You're absolutely correct. eM Client appears to be storing it with the
> quotes when I import the ics through there. I imported the same file
> through ownCloud and it seems to be working just fine now. Below is an
> example of an event as it exists in the db after import from eM
> Client.
Looked into the issue, and had a lot of trouble finding it at first.
Until I realized you were using a 1.5.* version..
Anyway, the problem is fixed. From what I understand you already devised a workaround yourself, but if you need it still, you can grab a copy here:
https://github.com/evert/SabreDAV/zipball/1.5
Cheers,
Evert
> This will be helpful for myself and others who are using the latest
> release of ownCloud, which shipped with the 1.5.* branch of SabreDAV.
> From what I read in the forums, the next release of ownCloud will
> incorporate the latest greatest SabreDAV. Thanks for the hard work on
> this great product :)
Thanks! :)
Evert