Edgewall Software

Opened 17 years ago

Closed 16 years ago

#1369 closed defect (wontfix)

iCalendar file not valid for Apple iCal 1.5

Reported by: quinn@… Owned by: Christopher Lenz
Priority: normal Milestone:
Component: roadmap Version: 0.9.4
Severity: normal Keywords: ical icalendar roadmap unreadable
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


I have an installation of Trac 0.8.1 and have just attempted to import the iCalendar for the roadmap into iCal and received the following error:

"33 of the events in this calendar file were unreadable. Events that were readable have been added to your iCal calendar."

The only events that were imported were my milestones, but none of the todos.

Any ideas?

Attachments (1)

roadmap.ics (11.1 KB ) - added by quinn@… 17 years ago.
The roadmap iCalendar file that could not be read.

Download all attachments as: .zip

Change History (11)

by quinn@…, 17 years ago

Attachment: roadmap.ics added

The roadmap iCalendar file that could not be read.

comment:1 by Christopher Lenz, 17 years ago

Milestone: 0.9
Status: newassigned

My guess is that the error is due to empty DESCRIPTION fields in ICS file. Do you know how many events were successfully imported from that file? Five?

comment:2 by Christopher Lenz, 17 years ago

Ah, re-reading the description I see that you say all the milestones were imported, of which there are five. None of the tickets have a description.

comment:3 by quinn@…, 17 years ago

Nope, that's not it. I added text to tall the description fields of the roadmap.ics file and it returned the same error. Yes, you're right it's just the VTODOs that are a problem VEVENTs import fine.

For comparison, here is a problem VTODO from trac, and followed by one exported from iCal so you can see the formatting difference.

From trac…

RELATED-TO:</projects/dcf/milestone/developer preview 0.5@www.strangecode.c
SUMMARY:Ticket #6: Datalog entries module
DESCRIPTION:No description

From iCal…

SUMMARY:Strangecode Support System
DESCRIPTION:user login accounts\nticketing\nhelp/documentation/faq\nnews

I can't work it out. Anybody have any ideas?

comment:4 by Christopher Lenz, 17 years ago

Resolution: worksforme
Status: assignedclosed

This works for me. I just subscribed to the ICS file you attached with iCal 2.0.1; all the tasks are showing up, and there's no error message. I've also yet to see an error message from any Trac install I use, being an iCal user myself.

comment:5 by mathieu, 16 years ago

Milestone: 0.91.0
Resolution: worksforme
Status: closedreopened

I reopen the bug. Doesn't work on iCal 1.5 (unless you tell me how to put iCal 2 on Panther).

comment:6 by Emmanuel Blot, 16 years ago

Milestone: 1.0

comment:7 by mathieu, 16 years ago

sorry if i did something wrong :( The problem for me is : tasks do not show up on ical1.5.5 . they appear in the ical file of course, but iCal does not show them. Tried with Sunbird, works ok. Perhaps something wrong in iCal interpretation of the format ? don't know…

comment:8 by Emmanuel Blot, 16 years ago

I guess that the first step is to understand which syntax makes iCal 1.5x sick. You are probably on your own to find this kind of trouble, as many people are using iCal 2.x now.

comment:9 by anonymous, 16 years ago

The iCal has problems with the "NEEDS-ACTION" value. Drop it and it will work. I just tracked a similiar problem down.

comment:10 by Christopher Lenz, 16 years ago

Resolution: wontfix
Status: reopenedclosed
Summary: iCalendar file not valid for Apple iCaliCalendar file not valid for Apple iCal 1.5

So, I don't see how we can fix this without removing the NEEDS-ACTION value even for clients that understand it. As doing so would arguably reduce the value of the exported data, I don't think that's acceptable.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Christopher Lenz.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Christopher Lenz to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.