1. 28 Oct, 2013 1 commit
    • Robert Rollins's avatar
      Issue #2107931: The Fields plugin now supports "First populated Date field". · 1e130962
      Robert Rollins authored
      Rather than defaulting an an illegal value, the Fields plugin's settings
      form now offers "First populated Date field" as the default option for
      "Date field". Using this option will tell Date iCal to look through all the
      fields in the View until it finds a populated Date field, and use that field.
      So, if there are two Date fields specified in the view's FIELDS setting, and
      at runtime the value of the first one is empty (e.g. because the node
      doesn't use that field), then the second Date field's value will be used.
  2. 18 Oct, 2013 1 commit
    • Robert Rollins's avatar
      Initial commit of Date iCal 3.0! · 11f49c89
      Robert Rollins authored
      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.
  3. 17 Oct, 2013 1 commit
    • Robert Rollins's avatar
      Issue [#2113513]: Users may now exclude the DTSTAMP field from their feeds. · 3073af84
      Robert Rollins authored
      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.
  4. 16 Oct, 2013 1 commit
  5. 03 Oct, 2013 1 commit
  6. 26 Sep, 2013 1 commit
    • Robert Rollins's avatar
      Issue [#2098051]: UIDs are now persistent across multiple retrievals of the ical feed. · 065cfa3d
      Robert Rollins authored
      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.
  7. 21 Aug, 2013 1 commit
  8. 24 Jul, 2013 1 commit
  9. 01 Jul, 2013 1 commit
  10. 27 Jun, 2013 2 commits