This may be covered in a different bug but I didn't see one that was exactly this issue.

The .ics file has some entries like:

BEGIN:VEVENT
DTSTAMP:20140608T060726Z
DTSTART;TZID=Mountain Standard Time;VALUE=DATE:20140613
DTEND;TZID=Mountain Standard Time;VALUE=DATE:20140613
STATUS:Confirmed
SUMMARY:Sunrise UMC Mission Team
DESCRIPTION:1--7-14 Janet Mawhirter
phMission team from Colorado Springs - \n30-50 people - adults &amp\; h
igh school - to sleep wherever they can. Would like freezer &amp\; frig sp
ace - need kitchen to fix meals - will shower at YMCA - will use classro
oms and sanctuary for small groups and worship in the evenings.
UID:73895419-261204308-20140613
END:VEVENT

After the feed has been imported, the Start date will be 14 June 2014 with an end date of 13 June 2014

The result being that a calendar display spans two days. Just seems odd to have the end date be the day before the start date.

Other than this small issue, it is working great for me.

CommentFileSizeAuthor
testfile.ics_.txt163.09 KBdougm
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

coredumperror’s picture

I'm guessing that you're exporting that ics file from Outlook? Outlook has some significant problems with it's iCal export functionality, and I'm afraid this is one of them. The iCal spec states that a 1-day event must have it's DTEND value set one day after it's DTSTART value, but your ics file has them both on the same day. Date iCal works under the assumption that the ics file it's importing follows the spec, and in order to make the Date All Day module display the event properly, it subtracts a day from the DTEND for All Day events. That's how the end date ends up being a day before the start date on your imports.

So unless you can convince your ics source to follow the spec, I'm afraid that this problem can't really be fixed.

dougm’s picture

Thanks. It is a commercial site but they do tend to cater to Outlook users. I'll file a problem report with them and will try to work around it for now.

coredumperror’s picture

Status: Active » Closed (won't fix)

Closing this issue as cleanup. Re-open if needed.