On my iCal feed from Google, mapping VEVENT or DTSTART / DTEND is causing cron to get stuck. I think I have figured out causes, I am just not sure what to do about it.

Here is a sample of my iCal feed:

BEGIN:VEVENT
DTSTART;VALUE=DATE:20090417
DTEND;VALUE=DATE:20090418
DTSTAMP:20091017T155619Z
UID:ajc0v0j56587ab39or6uflmjro@google.com
CREATED:20090317T115658Z
DESCRIPTION:
LAST-MODIFIED:20090317T115711Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Friday Nite Worship - High Point
TRANSP:TRANSPARENT
END:VEVENT
BEGIN:VEVENT
DTSTART:20081126T153000Z
DTEND:20081126T193000Z
DTSTAMP:20091017T155619Z
UID:kdfe4559nb4q821f4llc766je4@google.com
CREATED:20081120T182029Z
DESCRIPTION:
LAST-MODIFIED:20081120T182035Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:YAC Outting
TRANSP:OPAQUE
END:VEVENT

I have figured out that some events have DTSTART;VALUE=DATE:20090417 and others have only DTSTART:20081122T000000Z.

The default value type for DTSTART is DATE-TIME, but 20090417 is not a DATE-TIME.

One more thing, when I remove whatever Date field I am mapping, be it VEVENT to iCal parser or DTSTART to Date Start, cron works fine. When I try to bring any type of date into the equation cron flips out.

Please help! I've been trying to fix this for 3 straight days now and no one seems to be interested in helping!

Comments

Branjawn’s picture

Branjawn commented
Category: support » bug
johnmunro’s picture

johnmunro commented

It is quite possible that the php process is running over it's alloted time limit due to the extra mapping work required. Do a manual 'Refresh' to find out.

Branjawn’s picture

Branjawn commented
Status: Active » Closed (fixed)

I've moved on and done so many things that I can't even recreate this exact scenario. I am however still having issues. But for now I'll close this issue until I can readdress it. Thanks for the offer of assistance.