Tickets :: Comment on [#12773] Horde_Timezone unable to use non-ftp scheme to access database.

* Your Email Address
* Spam protection	Enter the letters below: .__ .__..___. ..___. [__)\| \|[__ \|_/ \| [__)\|__\|\| \| \ \|
Comment	>>> Hi Michael , whatever the reason is, it need to be fixed, cause its a >>> real showstopper for using Horde with Thunderbird Lightning. There is >>> a ticket at Mozilla about it too, so what can be done to get this >>> fixed. >> >> Well, first of all, the sample ics files you posted below are not >> complete. The first one is missing the full vTIMEZONE component. >> Second of all, if I import a complete ics file, with the proper >> components, and then export it, I get the correct time values. The >> following is a kronolith export of the event described by your sample >> ics file: >> >> BEGIN:VCALENDAR >> VERSION:2.0 >> X-WR-CALNAME:Yopopipip >> PRODID:-//The Horde Project//Horde iCalendar Library//EN >> BEGIN:VEVENT >> DTSTART;TZID=Europe/Berlin:20131021T140000 >> DTEND;TZID=Europe/Berlin:20131021T150000 >> DTSTAMP:20140206T140923Z >> UID:6824a851-a5c8-4b1c-aa66-5da72756d071 >> CREATED:20140206T140716Z >> LAST-MODIFIED:20140206T140716Z >> SUMMARY:Mo-14-15 >> DESCRIPTION:Mo-14-15 >> CLASS:PUBLIC >> STATUS:CONFIRMED >> TRANSP:OPAQUE >> RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO >> END:VEVENT >> BEGIN:VTIMEZONE >> TZID:Europe/Berlin >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19160430T230000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19161001T010000 >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19170416T020000 >> RRULE:FREQ=YEARLY;BYMONTH=4;BYMONTHDAY=15,16,17,18,19,20,21;BYDAY=1MO;UNTIL >> =19180421T00000Z >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19170917T020000 >> RRULE:FREQ=YEARLY;BYMONTH=9;BYMONTHDAY=15,16,17,18,19,20,21;BYDAY=1MO;UNTIL >> =19180915T00000Z >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19400401T020000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19421102T020000 >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19430329T020000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19431004T020000 >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19440403T020000 >> RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1MO;UNTIL=19450401T01000Z >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19441002T020000 >> TZNAME:CE-T >> END:STANDARD >> BEGIN:STANDARD >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0100 >> DTSTART:19450916T020000 >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0300 >> DTSTART:19450524T020000 >> TZNAME:CEMT >> END:DAYLIGHT >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0300 >> TZOFFSETTO:+0200 >> DTSTART:19450924T030000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19451118T020000 >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19460414T020000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19461007T020000 >> TZNAME:CE-T >> END:STANDARD >> BEGIN:STANDARD >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0100 >> DTSTART:19471005T020000 >> RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=1SU;UNTIL=19491002T01000Z >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19470406T030000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0300 >> DTSTART:19470511T020000 >> TZNAME:CEMT >> END:DAYLIGHT >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0300 >> TZOFFSETTO:+0200 >> DTSTART:19470629T030000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0200 >> DTSTART:19480418T020000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0200 >> DTSTART:19490410T020000 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19800406T010000 >> RRULE:FREQ=YEARLY;BYMONTH=4;BYDAY=1SU;UNTIL=19800406T00000Z >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19800928T010000 >> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9;UNTIL=19950923T23000Z >> TZNAME:CE-T >> END:STANDARD >> BEGIN:DAYLIGHT >> TZOFFSETFROM:+0100 >> TZOFFSETTO:+0200 >> DTSTART:19810329T010000 >> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 >> TZNAME:CEST >> END:DAYLIGHT >> BEGIN:STANDARD >> TZOFFSETFROM:+0200 >> TZOFFSETTO:+0100 >> DTSTART:19961027T010000 >> RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 >> TZNAME:CE-T >> END:STANDARD >> END:VTIMEZONE >> END:VCALENDAR >> > > > export and import ics file might not the same as upload events via > caldav from lightning to horde and vice versa, but this is where the > "bug" happens > > >
Attachment
Watch this ticket

Saved Queries