- 08 Sep, 2015 2 commits
-
-
Robert Rollins authored
-
Robert Rollins authored
-
- 20 Jul, 2015 2 commits
-
-
Robert Rollins authored
-
Robert Rollins authored
Thanks go to d.o user MegaChriz for this fix!
-
- 04 May, 2015 1 commit
-
-
Robert Rollins authored
Issue #2482643: Updated README and drush makefile to account for iCalcreator non-backwards compatibility. iCalcreator v2.22 is not backwards compatible with v2.20.0 and earlier, meaning it doesn't work with Date iCal. Many thanks go to d.o user bjlewis2 for pointing that out.
-
- 13 Apr, 2015 1 commit
-
-
Robert Rollins authored
Previously, the time value was pulled from the Date field, rather than the RDATE field. Now it'll pull from the RDATE field if it has a time, and fall back on the Date field if RDATE doesn't.
-
- 07 Apr, 2015 1 commit
-
-
Robert Rollins authored
Because the iCal spec states that VFREEBUSY components can't have the SUMMARY property, Date iCal will now fall back to the COMMENT property for the node title. Unfortuantely, this is the best we can do, becaise iCalcreator completely leaves out the SUMMARY property on VFREEBUSY componeents, so there's no way to recover it.
-
- 26 Mar, 2015 2 commits
-
-
Robert Rollins authored
-
Robert Rollins authored
-
- 06 Mar, 2015 2 commits
-
-
Robert Rollins authored
-
Robert Rollins authored
-
- 07 Oct, 2014 1 commit
-
-
Robert Rollins authored
-
- 22 Sep, 2014 1 commit
-
-
mglaman authored
Thanks go to user mgalman for the patch!
-
- 25 Aug, 2014 2 commits
-
-
Robert Rollins authored
iCalcreator knows that certain iCal properties (e.g. ATTENDEE) can have multiple entries in a single VEVENT. So when you access ATTENDEE for the first time, it gives you the first entry. Accessing it a second time gives back the second entry, or at least it tries to. If there is no second entry, iCalcreator returns False. Since Date iCal does not yet support multi-entry properties, I had to work around this functionality to ensure that hooks which add custom mappings don't run afoul of this process.
-
cdmo authored
This patch is courtesy of Drupal user cdmo.
-
- 25 Jun, 2014 1 commit
-
-
byrond authored
-
- 24 Jun, 2014 1 commit
-
-
t0xicCode authored
Thank you t0xicCode for this patch!
-
- 30 May, 2014 3 commits
-
-
Robert Rollins authored
-
Robert Rollins authored
-
Robert Rollins authored
-
- 27 May, 2014 1 commit
-
-
Robert Rollins authored
-
- 08 May, 2014 1 commit
-
-
Robert Rollins authored
User RedEight pointed out that I messed up the parse regex for UNTIL values when I made the recent change regarding DATE-type UNTILs. That's fixed, now. In addition, I tweaked the iCalcreator version detection regex to be a bit more forgiving of any possible changes the author makes in his version definition code.
-
- 23 Apr, 2014 1 commit
-
-
Robert Rollins authored
-
- 18 Apr, 2014 1 commit
-
-
Robert Rollins authored
-
- 16 Apr, 2014 6 commits
-
-
Robert Rollins authored
There's a new setting on the "iCal parser" settings page, which lets you set an integer number of days. Events which ended more than that number of days before the import will be skipped.
-
Robert Rollins authored
This makes it consistent with the "DateField: Repeat Rule" feeds target offered by the Date module. It also pushes the source up next to the "Date: Start" and "Date: End" sources, which helps you find it when you're setting up your mapping. This is only a UI change.
-
Robert Rollins authored
According to the iCal spec, the UNTIL value of an RRULE must be specified in UTC. But certain iCal feed creation tools don't respect this rule, and instead specify the UNTIL value in local time. Since all the other code that Date iCal utilizes to parse RRULEs expects the UNTIL value to be in UTC, this go badly when it's not. In order to get around this issue, I've added an option to the iCal Parser settings, which allows users to tell Date iCal that they expect the UNTIL values in their feeds' RRULEs to not be in UTC. With that option enabled, Date iCal will treat the UNTIL date as being in the same timezone as the event's DTSTART.
-
Robert Rollins authored
Upon further research, I discovered that my previous write-up about this setting was incomplete and partially incorrect. I also discovered the glaring bugs in the "Date's time zone" setting, so I added a warning against using it.
-
Robert Rollins authored
Date iCal doesn't currently use this new mechanism (I originally created it for a feature that ultimately didn't end up needing it), but it may be helpful in the future for when one handler needs to know about the results from a previous handler's pass over the same event.
-
Robert Rollins authored
-
- 14 Apr, 2014 1 commit
-
-
Robert Rollins authored
All day events which start on the last day of a month and don't have an end date specified were broken, due to a silly mistake I made in the DTEND emulation.
-
- 10 Apr, 2014 1 commit
-
-
Robert Rollins authored
-
- 31 Mar, 2014 1 commit
-
-
Robert Rollins authored
This hook allows modules to alter the final data array for each event, just before it gets sent through the rest of the Feeds processing steps to be turned into a node. The context array is what separates this hook's functionality from what users can do with Feeds Tamper.
-
- 24 Mar, 2014 1 commit
-
-
Robert Rollins authored
Made a few other improvements to the README while I was at it.
-
- 20 Feb, 2014 1 commit
-
-
Robert Rollins authored
-
- 03 Feb, 2014 3 commits
-
-
Robert Rollins authored
-
Robert Rollins authored
-
Robert Rollins authored
By using the amazing, free database of Windows timezone names curtesy of the CLDR project (http://cldr.unicode.org), I was able to add support for the non-standard timezone names created by Microsoft Outlook. Hopefully, the "not a valid timezone" error will now be much less common.
-
- 13 Dec, 2013 1 commit
-
-
Reinette authored
-
- 09 Dec, 2013 1 commit
-
-
Robert Rollins authored
-