Closed Bug 310284 Opened 19 years ago Closed 19 years ago

Multiple VCALENDAR entries in published .ics files

Categories

(Calendar :: Internal Components, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: s.wilson, Assigned: gray)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412.7 (KHTML, like Gecko) Safari/412.5
Build Identifier: 

Published iCalendar files contain multiple sets of VCALENDAR entries, sometimes one per VEVENT. This 
causes interoperability issues with iCal on Tiger, which complains of the subscribed calendar being invalid

Reproducible: Sometimes
Scott, does this happen with Sunbird 0.2, a Sunbird nightly build (which one) or
with the calendar extension (which version). 

If it's the first or the last, then please download a Sunbird nightly build at:
http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk 

There have been various checkins to the backend code in this area since the
release of Sunbird 0.2, so this may already be fixed.
This is with the Sunbird binaries, v0.2 for Windows. Is it worth waiting for a new stable build? 

(In reply to comment #1)
> Scott, does this happen with Sunbird 0.2, a Sunbird nightly build (which one) or
> with the calendar extension (which version). 
> 
> If it's the first or the last, then please download a Sunbird nightly build at:
> http://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk 
> 
> There have been various checkins to the backend code in this area since the
> release of Sunbird 0.2, so this may already be fixed.
Ok, marking INVALID for now.
Please wait until we release the 0.3alpha 1 release, which should be available
in the next 2-3 three weeks.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Component: libical → Internal Components
The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!
QA Contact: libical → base
You need to log in before you can comment on or make changes to this bug.