This new version is still in a state of partial completeness. You may need to do
some manual fixing to get it working, due to a change I made in the classes
offered by this module. Try 'drush cc registry' if 'drush cc all' fails.

Please note that ALL of the hooks exposed by Date iCal have changed. They do
essentially the same things they used to do, but they're named differently.

The big change is that the Feeds plugin has been completely re-written to
conform to the Feeds APIs. It's now much more resilient and powerful. Feeds
Tamper will now work, and is in fact the prescribed way to alter data, since I
removed several alter hooks.

Some ical feed readers will erroneously take the DTSTAMP field into
consideration when comparing a new download to a previous one, and end up
treating all events as having been updated, because their DTSTAMP field is
different. This new option lets you get around those buggy readers.

I also added the CREATED field, which was embarassingly missing until now.

LAST-MODIFIED was only being included if $entity->changed was set, and there
may have been some cases where that wasn't true. Now, LAST-MODIFIED will be
included based on $entity->created, if $entity->changed isn't set.

Much like in issue [#1935820], Date's bizarre implementation for repeating date
values was causing every VEVENT with an RRULE to be duplicated for each repeat.
I fixed the Fields plugin the same way that vlad fixed Entity.

According to the spec, EXDATE properties can have multiple values. However, many
popular calendar client don't support that, and only accept iCal feeds which
use multiple separate EXDATE properties. That is spec-compliant, though, so I
refactored Date iCal to do that for EXDATEs and RDATEs.

The previous fix that I applied for issue #2070883 was the complete wrong way to
go about fixing that problem, because it introduced a new, much more sinister
issue: the UID for an event would change every time the iCal feed got downloaded.

According to the spec, the UID is supposed to be persistent, so I re-engineered
the algoithm that creates UIDs for the Fields plugin so it will create the same
UIDs as the Entity plugin does.

iCalcreator requires that you *not* call createTimezone($vcal, 'UTC'), because
the spec says to use zulu time rather than a UTC VTIMEZONE object.

Also fixed a copy-pasta bug that probably never manifested, since it would have
only had an effect on events that have an end date that's in a different
timezone from the start date.

Also updated the README to reference the iCalcreator GitHub.

Issue [#2046935]: Added support for "long text" and "long text and summary" for the LOCATION and SUMMARY fields.

date_repeat_split_rrule() calls functions from other .inc files, but doesn't
directly load those files. So I made Date iCal load them before calling it.

Added a version number to help me determine which version of Date iCal is being used by something who's having problems.

Added the hook_date_ical_post_render() alter hook.

Issue [#2018285]: Optimized the method by which the feeds parser reads data from the incoming iCal feed.

This hook allows modules to fix broken timezone strings in the iCal feeds they import.

Also cleaned up the way that timezone strings are handled by the parser, especially under error conditions.

date_ical_format_text() was going way overboard on it's attempts
to make text iCal compliant. I got rid of all the escaping, and also
all the extra endlines which the drupal function was adding at 80-char
boundries.

I added the summary_field option to option_definition, which should
fix several (surprisingly unreported) errors related to Features and first-time
setup.

Added the view object as a parameter for theme_date_ical_icon, which gives
additional context for any module that would like to override that theme.