/ - Diff - Club Drupal - Forge Centrale Marseille

     This module allows users to export iCal feeds using Views, and import iCal feeds
     from other sites using Feeds. Any entity that contains a Date field can act as
     the source of events for an iCal feed.
     the source/target to export/import an iCal feed.
     ===============================================================================
     INSTALLATION
-...
     - The Feeds module is optional. It's needed only if you you wish to import iCal
       feeds from other sites.
     To install the iCalcreator library, download it from the project's github:
     http://github.com/iCalcreator/iCalcreator
     Using either git clone or the "Download Zip" button, you'll find the file
     iCalcreator.class.php inside. Copy that file to a folder in your Drupal site
     named sites/all/libraries/iCalcreator.
     To install the iCalcreator library, download the project's official zip file:
     https://github.com/iCalcreator/iCalcreator/archive/master.zip
     Extract it, and copy iCalcreator.class.php to a folder in your Drupal site
     named sites/all/libraries/iCalcreator (you'll need to create that folder).
     Or, if you have drush, install iCalcreator by running this command from your
     site's root directory:
     Or, if you have drush, you can install iCalcreator by running this command from
     your site's root directory:
     drush make sites/all/modules/date_ical/date_ical.make --no-core
     Then, clear the cache on your site by using either "drush cc all" or logging in
-...
         size, include additional information from other fields, etc.
 .  Do this for each of the content types that you wish to include in your
         site's iCal feeds.
 .  Create a new View that displays the entities that you want to include in the
         iCal feed.
 .  Add a "Feed" to the view. Change the Format to "iCal Feed". When you click
         Apply from that dialog, you'll be given the option to name the calendar,
         which will appear in your users' calendar clients as the calendar's title.
 .  Create a new View that displays the entities that you want to include in
         the iCal feed.
 .  Add a "Feed" display to the same View. Change the Format to "iCal Feed".
         When you click "Apply" from that dialog, you'll be given the option to name
         the calendar, which will appear in your users' calendar clients as the
         calendar's title.
 .  Change the Show setting to "iCal Entity".
 .  In the settings for iCal Entity, select the date field that should be used
         as the event date for the iCal feed. Make sure that you choose a field that
         is a part of every entity that your View displays. Otherwise, the entities
         which don't have that field will be left out of the iCal feed.
 .  You may optionally choose a field that will be used to populate the Location
         property of events in your iCal feed. This field can be a text field, a
         Node Reference field, an Addressfield, or a Location field.
 . Give the feed a path like 'calendar/%/export.ics', including a '/%/' for
 .  You may optionally choose a field that will be used to populate the
         Location property of events in your iCal feed. This field can be a text
         field, a Node Reference field, an Addressfield, or a Location field.
 . Give the Feed a path like 'calendar/%/export.ics', including a '/%/' for
         every contextual filter in the view.
 . Make sure the Pager options are set to "Display all items".
 . Add date filters or arguments that will constrain the view to the items you
         want to be included in the iCal feed.
 . Attach the feed to a another view (usually a Page view that is displaying
         the same events). Be aware, though, that attaching the feed to a view with
         different output will not make the iCal feed include that output. It will
         always include the events which match the feed's filters.
 . Using the "Attach to:" setting in the Feed Settings panel, attach the feed
         to a another display in the same view (usually a Page display). Be aware,
         though, that the Feed will display exactly what its settings tell it to,
         regardless of how the Page display is set up. Thus, it's best to ensure
         that both displays are configured to include the same content.
 . Save the View.
 . Navigate to a page which displays the attached view. You should see the iCal
         icon at the bottom of the view's output. Clicking on the icon will subscribe
         your preferred calendar app to the iCal feed. However, if you don't have a
         calendar app set up on your computer, you'll want to go back to the View
         settings page, click the Settings link next to "Format: iCal Feed", and check
         "Disable webcal://", then save your View. This will make the iCal icon
         download a .ics file with the events, instead of loading the events directly
         into a calendar app.
 . Navigate to a page which displays the view (usually the Page display's
         "path" setting). You should see the iCal icon at the bottom of the view's
         output. Clicking on the icon will subscribe your calendar app to the iCal
         feed.
 . If you don't have a calendar app set up on your computer, or you want your
         users to download the ical feed rather than subscribe to it, you'll want to
         go back to the View settings page, click the Settings link next to
         "Format: iCal Feed", and check "Disable webcal://". Then save your View.
         This will make the iCal icon download a .ics file with the events, instead
         of loading the events directly into the user's calendar app.
     HOW TO EXPORT AN ICAL FEED USING THE iCal Fields PLUGIN
 -6.These steps are the same as above.
-...
         your iCal feed with. A Date field is required, and fields that will act as
         the Title and Description of the events are reccomended. You can also
         include a Location field.
 .  Back in the FORMAT section, change the Show setting to 'iCal Fields'.
 .  Back in the FORMAT section, change the "Show" setting to 'iCal Fields'.
 .  In the settings for iCal Fields, choose which views fields you want to use
         for the Date, Title, Description, and Location.
 + These steps are the same as above.
-...
          you add any more mappings, click "Save" at the bottom of the page.
 ) It's a good idea to map the "Summary/Title" source to the "Title" target,
          and the "Description" source to whatever field is the "body" of the node.
 ) As of 2014/02/03 there is a major bug in Feeds that leaves the Date
          values on all imported events blank. You must update your Feeds module
          to the dev release (https://drupal.org/node/927032) to overcome this bug.
 ) AS OF 2014/04/10 THERE IS A MAJOR BUG IN Feeds WHICH LEAVES THE DATE
          VALUES ON ALL IMPORTED EVENTS BLACNK. YOU MUST APPLY A PATCH TO Feeds
          TO FIX THIS PROBLEM. IT IS AVAILABLE HERE: http://drupal.org/node/2237177.
     - Once you've completed all the mappings, click the "Save" button on the
       bottom left side of the page.
     - Now you can import the iCal feed into nodes by going to the /import page of
       your site (e.g. http://www.exmaple.com/import). Click the link for the
       importer you just created, and enter the URL of the feed you'd like to
       import into the "URL" field. Click the "Import" button, and observe the
       progress.
       importer you just created, and enter the URL of the feed into the "URL"
       field. Click the "Import" button, and observe the progress.
     - Once it's done, you should see a green message saying "Created X nodes." If
       you do, you've successfully set up your iCal importer. If you get some other
       message, you'll need to tweak the importer's settings.
-...
     Remember, you have to map the UID source to the GUID target, and make it
     unique, or your imports won't work!
     IMPORTANT NOTE:
     If you're building a site that will be viewed by out-of-state users, and you
     allow said users to set their own timezone, you'll want to set up your Date
     fields to use the "Date's time zone" option. If you don't, then users who live
     in a different timezone will be shown the times for your events in their local
     timezone, rather than your events' timezone. This makes sense if your events
     will be broadcast live to these out-of-state users, but if they need to travel
     to your event, they may end up arriving at the wrong time.
     ===============================================================================
     IMPORTANT NOTE ABOUT THE DATE FIELD TIMEZONE SETTING
     ===============================================================================
     Date fields have a setting called "Time zone handling" which determines how
     dates are stored in the database, and how they are displayed to users.
      - "Site's time zone" converts the date to UTC as it stores it to the DB. Upon
       display, it converts the date to the "Default time zone" that's set on your
       site's Regional Settings configuration page (/admin/config/regional/settings).
      - "Date's time zone" stores the date as it is entered, along with the timezone
       name. Upon display, it converts the date from the stored timezone into the
       site's default timezone. Well, I'm pretty sure it's *supposed* to do that, but
       the code behind this setting is very buggy. DO NOT USE THIS SETTING.
      - "User's time zone" converts the date to UTC as it stores it to the DB. Upon
       display, it converts the date to the current user's timezone setting.
      - "UTC" converts the date to UTC as it stores it to the DB. Upon display, it
       performs no conversion, showing the UTC date directly to the user.
      - "No time zone conversion" performs no conversion as it stores the date in
       the DB. It also performs no conversion upon display.
     The appropriate setting to choose here will depend upon how you want times to
     be displayed on your site. The best setting *would* be "Date's time zone",
     but since that setting is so buggy, I must recommend against it. Instead,
     I'd suggest using "Site's time zone" for sites which host events that are
     mostly in the same timezone (set the site's default timezone appropriately).
     This works just right for local users of your site, and will be the least
     confusing for users who live in a different timezone.
     For sites which store events that take place in multiple different timezones,
     the "User's time zone" setting is probably the most appropriate. Most users will
     presumably be tuning in to your events online or on TV (since many take place
     far away from them), which means they'll want to know what time the event occurs
     in their local timezone, so they don't miss the broadcast.
     If your Date field is already set to "Date's time zone", you won't be able to
     change it, because that setting uses a different table schema than the others.
     Since "Date's time zone" is very buggy, I'd strongly recomend deleting the
     field and recreating it with a different setting. This will delete all the
     dates in existing event nodes which use this field.
     ===============================================================================
     HOW TO FIX THE "not a valid timezone" ERROR
-...
     Replace <module> with the name of your module, change the code to do whatever
     needs to be done to fix your timezones, and clear your Drupal cache.
     ===============================================================================
     ADDITIONAL NOTES
     ===============================================================================
     Date iCal only supports outputting iCal calendars through Views.
     Date iCal only supports exporting iCal calendars by using Views.
     To put an "Add to calendar" button on individual event nodes, try the
     Add to Cal module (http://drupal.org/project/addtocal), or follow the
     instructions created by the estimable nmc at:

      *****************************************************************************/
     /**
      * Alter the vcalendar object created from an imported iCal feed.
      * Alter the vcalendar object imported from an iCal feed.
+     *
      * @param object $calendar
      *   An instance of the iCalcreator library's vcalendar class.
-...
+    }
     /**
      * Alter a calendar component created from an imported iCal feed.
      * Alter a calendar component imported from an iCal feed.
+     *
      * @param object $component
      *   This will usually be an iCalcreator vevent object, but Date iCal also
-...
+      }
+    }
     /**
      * Alter the parsed data for an event imported from an iCal feed.
+     *
      * @param array $data
      *   An associative array of field data that represents an imported event.
      * @param array $context
      *   An associative array of context, with the following keys and values:
      *   - 'calendar': The iCalcreator vcalendar parent object of this component.
      *   - 'source': FeedsSource object for this Feed.
      *   - 'fetcher_result': The FeedsFetcherResult object for this Feed.
      */
     function hook_date_ical_import_post_parse_alter(&$data, $context) {
       // Example of what might be done with this alter hook.
       if (!empty($context['calendar']->xprop['X-WR-CALNAME']['value'])) {
         // Do something with the calendar name....
+      }
+    }
     /**
      * Alter the timezone string from an imported iCal Feed.
+     *

     ; Includes for iCal feed import using Feeds
     files[] = includes/DateiCalFeedsParser.inc
     ; Information added by Drupal.org packaging script on 2014-02-04
     version = "7.x-3.1"
     ; Information added by Drupal.org packaging script on 2014-05-30
     version = "7.x-3.2"
     core = "7.x"
     project = "date_ical"
     datestamp = "1391480015"
     datestamp = "1401492228"

      * value of the iCal feeds created by Date iCal. It's primarily used for
      * debugging.
      */
     define('DATE_ICAL_VERSION', '3.1');
     define('DATE_ICAL_VERSION', '3.2');
     /**
      * Exception class for generic exceptions thrown by this module.
-...
         'download url' => 'http://github.com/iCalcreator/iCalcreator',
         'version arguments' => array(
           'file' => 'iCalcreator.class.php',
           'pattern' => "/define\( 'ICALCREATOR_VERSION', 'iCalcreator ([\d\.]+)' \);/",
           'pattern' => "/define.*?ICALCREATOR_VERSION.*?([\d\.]+)/",
           'lines' => 100,
         ),
         'files' => array(

       $start_datetime = date_format($start, DATE_FORMAT_DATETIME);
       if (!empty($rrule_values['UNTIL']['datetime'])) {
         // TODO: The spec says that UNTIL must be specified in UTC, but I think
         // this may not be followd by all feed creators. It may be a good idea to
         // support optionally assuming the date has the same TZID as DTSTART.
         $end = date_ical_date($rrule_values['UNTIL'], $timezone);
         $end_datetime = date_format($end, DATE_FORMAT_DATETIME);
         // The spec says that UNTIL must be in UTC, but not all feed creators
         // follow that rule. If the user specified that he wanted to overcome this
         // problem, use $timezone for the $final_repeat, and then convert the UNTIL
         // in the unparsed RRULE to UTC.
         if (!empty($source->importer->config['parser']['config']['until_not_utc'])) {
           // Change the parsed UNTIL from UTC to $timezone, so that the
           // date_ical_date() won't convert it.
           $rrule_values['UNTIL']['tz'] = $timezone;
           // Convert the unparsed UNTIL to UTC, since the Date code will use it.
           // It may currently have a Z on it, but only because iCalcreator blindly
           // adds one to DATETIME-type UNTILs if it's not there.
           $matches = array();
           if (preg_match('/^(.*?)UNTIL=([\dT]+)Z?(.*?)$/', $repeat_data['RRULE'], $matches)) {
             // If the UNTIL value doesn't have a "T", it's a DATE, making timezone
             // fixes irrelvant.
             if (strpos($matches[2], 'T') !== FALSE) {
               $until_date = new DateObject($matches[2], $timezone);
               $until_date->setTimezone(new DateTimeZone('UTC'));
               $matches[2] = $until_date->format('Ymd\THis');
               $repeat_data['RRULE'] = "{$matches[1]}UNTIL={$matches[2]}Z{$matches[3]}";
+            }
+          }
           else {
             watchdog('date_ical', 'The RRULE string "%rrule" could not be parsed to fix the UNTIL value. Date repeats may not be calculated correctly.',
               array('%rrule' => $repeat_data['RRULE']), WATCHDOG_WARNING
             );
+          }
+        }
         $final_repeat = date_ical_date($rrule_values['UNTIL'], $timezone);
         $final_repeat_datetime = date_format($final_repeat, DATE_FORMAT_DATETIME);
+      }
       elseif (!empty($rrule_values['COUNT'])) {
         $end_datetime = NULL;
         $final_repeat_datetime = NULL;
+      }
       else {
         // No UNTIL and no COUNT?
         // No UNTIL and no COUNT? This is an illegal RRULE.
         return array();
+      }
-...
         $date = date_ical_date($rdate, $timezone);
         $additions[] = date_format($date, 'Y-m-d');
+      }
       // TODO: EXRULE.
       // TODO: EXRULEs.
       $date_repeat_compatible_rrule = "{$repeat_data['RRULE']}\n{$repeat_data['RDATE']}\n{$repeat_data['EXDATE']}";
       $calculated_dates = date_repeat_calc($date_repeat_compatible_rrule, $start_datetime, $end_datetime, $exceptions, $timezone, $additions);
       $calculated_dates = date_repeat_calc($date_repeat_compatible_rrule, $start_datetime, $final_repeat_datetime, $exceptions, $timezone, $additions);
       $repeat_dates = array();
       foreach ($calculated_dates as $delta => $date) {
         // date_repeat_calc always returns DATE_DATETIME dates, which is
-...
           continue;
+        }
         // These keys never have multiple values.
         // The following keys never have multiple values.
         if (in_array($key, array('UNTIL', 'FREQ', 'INTERVAL', 'COUNT', 'WKST'))) {
           if ($key == 'UNTIL') {
             // This is a function from the date_api module, not date_ical.

           throw new DateIcalException(t('Parsing the data from %url failed. Please ensure that this URL leads to a valid iCal feed.', array('%url' => $url)));
+        }
         // Total hack to get around iCalcreator's mistreatment of UID "0".
         if (empty($calendar->components[0]->uid) || empty($calendar->components[0]->uid['value'])) {
           $calendar->components[0]->uid = array('value' => 'zero', 'params' => NULL);
+        }
         // Allow modules to alter the vcalendar object before we interpret it.
         $context = array(
           'source' => $source,
-...
       public function sourceDefaults() {
         return array(
           'indefinite_count' => $this->config['indefinite_count'],
           'until_not_utc' => $this->config['until_not_utc'],
           'skip_days' => $this->config['skip_days'],
         );
+      }
-...
       public function configDefaults() {
         return array(
           'indefinite_count' => '52',
           'until_not_utc' => FALSE,
           'skip_days' => NULL,
         );
+      }
-...
           '#description' => t('Indefinitely repeating events are not supported. The repeat count will instead be set to this number.'),
           '#default_value' => $this->config['indefinite_count'],
         );
         $form['until_not_utc'] = array(
           '#title' => t('RRULE UNTILs are not in UTC'),
           '#type' => 'checkbox',
           '#description' => t('Enable this setting if your reccuring events are not repeating the correct number of times. ' .
               'The iCal spec requires that the UNTIL value in an RRULE almost always be specified in UTC, but some iCal feed creators fail to follow that rule ' .
               '(the UNTIL values in those feeds\' RRULEs don\'t end is "Z"). This causes the UNTIL value to be off by several hours, ' .
               'which can cause the repeat calculator to miss or add repeats.'),
           '#default_value' => $this->config['until_not_utc'],
         );
         $form['skip_days'] = array(
           '#title' => t('Skip events more than X days old'),
           '#type' => 'textfield',
           '#size' => 5,
           '#description' => t('Set this value to any positive integer (or 0) to skip events which ended more than that many days before the import. ' .
             'Leave it blank to import all events.'),
           '#default_value' => $this->config['skip_days'],
         );
         return $form;
+      }
       /**
        * Validation handler for configForm.
        */
       public function configFormValidate(&$source_config) {
         if (!preg_match('/^\d+$/', $source_config['skip_days']) && $source_config['skip_days'] !== '') {
           form_set_error('skip_days', 'You must enter a positive integer.');
+        }
         if ($source_config['skip_days'] === '') {
           $source_config['skip_days'] = NULL;
+        }
+      }
       /**
        * Creates the list of mapping sources offered by DateiCalFeedsParser.
        */
-...
           'date_ical_parse_handler' => 'parseDateTimeProperty',
         );
         $sources['RRULE'] = array(
           'name' => t('Repeat Rule'),
           'name' => t('Date: Repeat Rule'),
           'description' => t('The RRULE property. Describes when and how often this event should repeat.
             The date field for the target node must be configured to support repeating dates, using the Date Repeat Field module (a submodule of Date).'),
           'date_ical_parse_handler' => 'parseRepeatProperty',

           // Prevent devel module from appending queries to ical export.
           $GLOBALS['devel_shutdown'] = FALSE;
           drupal_add_http_header('Content-Type', 'text/calendar; charset=utf-8');
           drupal_add_http_header('Content-Type', 'text/calendar; charset=UTF-8');
           drupal_add_http_header('Cache-Control', 'no-cache, must-revalidate');
           drupal_add_http_header('Expires', 'Sat, 26 Jul 1997 05:00:00 GMT');
           // For sites with Clean URLs disabled, the Display's "path" value ends
           // up only in the query args, meaning the filename won't be set properly

       protected $timezones = array();
       protected $xtimezone;
       /**
        * The parsed data for the component that's currently being processed.
+       *
        * ParserVcalendar parses one component at a time. This array is stored as a
        * property so that each handler can tell what work the previous handlers
        * have already completed on the current component.
+       *
        * @var array
        */
       protected $parsed_data = array();
       /**
        * Variables used for batch processing.
        */
-...
       public function __construct($calendar, $source, $fetcher_result, $config) {
         $this->calendar = $calendar;
         $this->source = $source;
         $this->mapping_sources = feeds_importer($source->id)->parser->getMappingSources();
         $this->fetcherResult = $fetcher_result;
         $this->config = $config;
+      }
       /**
        * Parses the vcalendar object into an array of event data arrays.
+       *
-...
        *   Specifies how many components to parse on this run.
+       *
        * @return array
        *   An array of parsed event data keyed by the same strings as the array
        *   returned by DateiCalFeedsParser::getiCalMappingSources().
        *   An array of parsed event data keyed by our mapping source property keys.
        */
       public function parse($offset, $limit) {
         // Sometimes, the feed will set a timezone for every event in the calendar
-...
           $this->timezones[] = $component;
+        }
         // This content array is used by date_ical_import_component_alter() and
         // date_ical_import_parsed_data_alter().
         $context2 = array(
           'calendar' => $this->calendar,
           'source' => $this->source,
           'fetcher_result' => $this->fetcherResult,
         );
         // Collect each component, so we can batch them properly in the next loop.
         $raw_components = array();
         $types = array('VEVENT', 'VTODO', 'VJOURNAL', 'VFREEBUSY', 'VALARM');
-...
           while ($vcalendar_component = $this->calendar->getComponent($type)) {
             // Allow modules to alter the vcalendar component before we parse it
             // into a Feeds-compatible data array.
             $context = array(
               'calendar' => $this->calendar,
               'source' => $this->source,
               'fetcher_result' => $this->fetcherResult,
             );
             drupal_alter('date_ical_import_component', $vcalendar_component, $context);
             drupal_alter('date_ical_import_component', $vcalendar_component, $context2);
             $raw_components[] = $vcalendar_component;
+          }
+        }
-...
         // Parse each raw component in the current batch into a Feeds-compatible
         // event data array.
         $events = array();
         $sources = DateiCalFeedsParser::getiCalMappingSources();
         $batch = array_slice($raw_components, $offset, $limit, TRUE);
         foreach ($batch as $ndx => $raw_component) {
           $parsed_component = array();
           foreach ($sources as $property_key => $data) {
             $handler = $data['date_ical_parse_handler'];
             $parsed_component[$property_key] = $this->$handler($property_key, $raw_component);
           $this->parsed_data = array();
           foreach ($this->mapping_sources as $property_key => $data) {
             $handler = NULL;
             if (isset($data['date_ical_parse_handler'])) {
               $handler = $data['date_ical_parse_handler'];
+            }
             else {
               // This is not one of our sources, so if we don't recognize and
               // support it, we'll have to pass a warning to the user.
               if ($property_key == 'geofield') {
                 $handler = 'parseGeofield';
+              }
               else {
                 // We can safely ignore certain sources.
                 $known_unknowns = array(
                   // "Black Source 1" is from Feeds Tamper.
                   'Blank source 1',
                 );
                 if (!in_array($property_key, $known_unknowns)) {
                   // Only warn the user if this mapping source is in use.
                   foreach ($this->source->importer->processor->config['mappings'] as $mapping) {
                     if ($mapping['source'] == $property_key) {
                       drupal_set_message(t('Date iCal does not recognize the "@name" Mapping Source, and must skip it.', array('@name' => $data['name'])), 'warning', FALSE);
                       break;
+                    }
+                  }
+                }
+              }
+            }
             if ($handler) {
               $this->parsed_data[$property_key] = $this->$handler($property_key, $raw_component);
+            }
             if ($property_key == 'geofield' && !empty($this->parsed_data['geofield'])) {
               // To make our data readable by geofield_feeds_combined_source(), we
               // need to put it into the format output by Simplepie 1.3.
               $this->parsed_data['location_latitude'] = array($this->parsed_data['geofield']['lat']);
               $this->parsed_data['location_longitude'] = array($this->parsed_data['geofield']['lon']);
+            }
+          }
           // Allow modules to alter the final parsed data before we send it to the
           // Feeds processor.
           drupal_alter('date_ical_import_post_parse', $this->parsed_data, $context2);
           // Skip this event if it's earlier than the user's specified skip time.
           if (!$this->_skip_current_event()) {
             $events[] = $this->parsed_data;
+          }
           $events[] = $parsed_component;
           // The indices of the original $raw_components array are preserved in
           // $batch, so using the $ndx value here lets us communicate our progress
           // through the full collection of components.
-...
+      }
       /**
        * Parses text fields.
        * Handler that parses text fields.
+       *
        * @return string
        *   The parsed text property.
-...
         $text = str_replace(array('\n', '\N'), "\n", $text);
         return $text;
+      }
       /**
        * Parses field parameters.
        * Handler that parses GEO fields.
+       *
        * @return array
        *   The latitude and longitude values, keyed by 'lat' and 'lon'.
        */
       public function parseGeofield($property_key, $vcalendar_component) {
         $geo = array();
         if (!empty($vcalendar_component->geo['value'])) {
           $geo['lat'] = $vcalendar_component->geo['value']['latitude'];
           $geo['lon'] = $vcalendar_component->geo['value']['longitude'];
+        }
         return $geo;
+      }
       /**
        * Handler that parses field parameters.
+       *
        * @return string
        *   The parsed field parameter.
-...
           // If the component doesn't have this property, return NULL.
           return NULL;
+        }
         return isset($property['params'][$attr]) ? $property['params'][$attr] : '';
         $param = isset($property['params'][$attr]) ? $property['params'][$attr] : '';
         return $param;
+      }
       /**
        * Parses DATE-TIME and DATE fields.
        * Handler that parses DATE-TIME and DATE fields.
+       *
        * @return FeedsDateTime
        *   The parsed datetime object.
-...
               // If this is an all-day event with no end or duration, treat this
               // as a single-day event by emulating DTEND as 1 day after DTSTART.
               $property = $dtstart;
               $property['value']['day'] = $dtstart['value']['day'] + 1;
               $property['value'] = iCalUtilityFunctions::_duration2date($property['value'], array('day' => 1));
+            }
             else {
               // This event has no end date.
-...
               $property['value'] = $prev_day;
+            }
+          }
           // FeedsDateTime->setTimezone() ignores timezone changes made to dates
           // with no time element, which means we can't compensate for the Date
           // module's automatic timezone conversion when it writes to the DB. To
-...
             $datetimezone = new DateTimeZone(date_default_timezone_get());
+          }
+        }
         return new FeedsDateTime($date_string, $datetimezone);
         $datetime = new FeedsDateTime($date_string, $datetimezone);
         return $datetime;
+      }
       /**
        * Parses multi-value fields, like the CATEGORIES component.
        * Handler that parses multi-value fields, like the CATEGORIES component.
+       *
        * @return array
        *   An array of strings contaning the individual values.
-...
+        }
         return $property;
+      }
       /**
        * Format RRULEs, which specify when and how often the event is repeated.
        * Handler that parses RRULE, RDATE, EXRULE, and EXDATE together.
+       *
        * @return string
        *   An RRULE string, with EXDATE and RDATE values separated by \n.
        *   This is to make the RRULE compatible with date_repeat_split_rrule().
        *   The RRULE, RDATE, EXRULE, and EXDATE values concatinated with |.
        */
       public function parseRepeatProperty($property_key, $vcalendar_component) {
         if ($vcalendar_component->getProperty($property_key) === FALSE) {
           return NULL;
+        }
         $uid = $vcalendar_component->getProperty('UID');
         $count = $this->config['indefinite_count'];
         // Due to a few bugs and limitations with Date Repeat, we need to massage
         // the RRULE a bit.
         if (count($vcalendar_component->rrule) > 1) {
           drupal_set_message(t('The event with UID %uid has multiple RRULEs, but the Date Repeat module only supports one. Only the first RRULE in the event will be used.<br>
               If your events need to have a complex repeat pattern, using RDATEs should help.',
             array('%uid' => $vcalendar_component->getProperty('UID'))), 'warning'
           );
           $msg = 'The event with UID %uid has multiple RRULEs, but the Date Repeat module only supports one. Only the first RRULE in the event will be used.
             If your events need to have a complex repeat pattern, using RDATEs should help.';
           watchdog('date_ical', $msg, array('%uid' => $uid), 'warning');
           drupal_set_message('At least one of the events in this iCal feed has multiple RRULEs, but the Date Repeat module only supports one.
             Only the first RRULE in an event will be used.', 'warning', FALSE);
           // Date Repeat will get extremely confused if it's sent multiple RRULE
           // values, so we need to manually pare it down to only the first one.
           $vcalendar_component->rrule = array($vcalendar_component->rrule[0]);
-...
           if (!isset($rrule_data['value']['INTERVAL'])) {
             $rrule_data['value']['INTERVAL'] = '1';
+          }
           if (!isset($rrule_data['value']['COUNT']) && !isset($rrule_data['value']['UNTIL'])) {
             drupal_set_message(t("The event with UID %uid has an indefinitely repeating RRULE, which the Date Repeat module doesn't support.<br>
             $msg = "The event with UID %uid has an indefinitely repeating RRULE, which the Date Repeat module doesn't support.
               As a workaround, Date iCal set the repeat count to @count. This value can be customized in the iCal parser settings.";
             watchdog('date_ical', $msg, array('%uid' => $uid, '@count' => $count), WATCHDOG_WARNING);
             drupal_set_message(
               t("At least one of the events in this iCal feed has an indefinitely repeating RRULE, which the Date Repeat module doesn't support.<br>
                 As a workaround, Date iCal set the repeat count to @count. This value can be customized in the iCal parser settings.",
               array('%uid' => $vcalendar_component->getProperty('UID'), '@count' => $this->config['indefinite_count'])), 'warning'
               array('@count' => $count)),
               'warning',
               FALSE
             );
             $rrule_data['value']['COUNT'] = $this->config['indefinite_count'];
+          }
+        }
         $rrule = trim($vcalendar_component->createRrule());
         $rdate = trim($vcalendar_component->createRdate());
         $exrule = trim($vcalendar_component->createExrule());
         $exdate = trim($vcalendar_component->createExdate());
         return "$rrule|$rdate|$exrule|$exdate";
+      }
       /**
        * Internal helper function for creating DateTimeZone objects.
        */
-...
           $windows_to_olson_map = array();
           foreach ($zones_assoc['supplemental']['windowsZones']['mapTimezones'] as $mapTimezone) {
             if ($mapTimezone['mapZone']['_other'] == $tzid) {
               // $mapTimezone['mapZone']['_type'] is space-separated TZIDs.
               // Parse out the space-separated TZIDs from $mapTimezone['mapZone']['_type'].
               $tzids = preg_split('/\s/', $mapTimezone['mapZone']['_type']);
               try {
                 // They all have the same UTC offset, so for our purposes we can
-...
+        }
         return $datetimezone;
+      }
       /**
        * Internal helper function for skipping old events.
        */
       protected function _skip_current_event() {
         // Must use !isset() here, because 0 and NULL mean different things.
         if (!isset($this->config['skip_days'])) {
           return FALSE;
+        }
         $compare_date = isset($this->parsed_data['DTEND']) ? $this->parsed_data['DTEND'] : $this->parsed_data['DTSTART'];
         $skip_date = new FeedsDateTime("today -{$this->config['skip_days']} days", $compare_date->getTimezone());
         $skip = ($skip_date > $compare_date);
         return $skip;
+      }
+    }

     DESCRIPTION:This event uses a fake TZID and should throw the "not a valid timezone" warning at import time, and be treated as UTC.
     END:VEVENT
     BEGIN:VEVENT
     SUMMARY:Event w/ GEO
     DTSTART;TZID=America/New_York:20131009T190000
     DTEND;TZID=America/New_York:20131009T210000
     UID:date_ical_basic_test0E
     DESCRIPTION:This is a standard event that has a GEO field.
     GEO:34.1378534;-118.1252851
     END:VEVENT
     END:VALENDAR

     BEGIN:VCALENDAR
     PRODID:-//Google Inc//Google Calendar 70.9054//EN
     VERSION:2.0
     CALSCALE:GREGORIAN
     METHOD:PUBLISH
     X-WR-CALNAME:Events Feed
     X-WR-TIMEZONE:America/New_York
     X-WR-CALDESC:A calendar for the events feed
     BEGIN:VTIMEZONE
     TZID:America/New_York
     X-LIC-LOCATION:America/New_York
     BEGIN:DAYLIGHT
     TZOFFSETFROM:-0500
     TZOFFSETTO:-0400
     TZNAME:EDT
     DTSTART:19700308T020000
     RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
     END:DAYLIGHT
     BEGIN:STANDARD
     TZOFFSETFROM:-0400
     TZOFFSETTO:-0500
     TZNAME:EST
     DTSTART:19701101T020000
     RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
     END:STANDARD
     END:VTIMEZONE
     BEGIN:VEVENT
     SUMMARY:Event w/ Bad UNTIL
     UID:12345acbdef1
     DTSTART;TZID=America/Los_Angeles:20140323T190000
     DTEND;TZID=America/Los_Angeles:20140323T210000
     RRULE:FREQ=DAILY;UNTIL=20140328T190000;WKST=SU
     DESCRIPTION:description
     END:VEVENT
     BEGIN:VEVENT
     SUMMARY:Event w/ UTC UNTIL
     UID:12345acbdef2
     DTSTART;TZID=America/Los_Angeles:20140323T190000
     DTEND;TZID=America/Los_Angeles:20140323T210000
     RRULE:FREQ=DAILY;UNTIL=20140328T230000Z;WKST=SU
     DESCRIPTION:description
     END:VEVENT
     BEGIN:VEVENT
     SUMMARY:Event w/ COUNT
     UID:12345acbdef3
     DTSTART;TZID=America/Los_Angeles:20140323T190000
     DTEND;TZID=America/Los_Angeles:20140323T210000
     RRULE:FREQ=DAILY;COUNT=6;WKST=SU
     DESCRIPTION:description
     END:VEVENT
     BEGIN:VEVENT
     SUMMARY:Event w/ DATE-type UNTIL
     UID:12345acbdef4
     DTSTART;VALUE=DATE:20140323
     DTEND;VALUE=DATE:20140323
     RRULE:FREQ=DAILY;UNTIL=20140328;WKST=SU
     DESCRIPTION:description
     END:VEVENT
     END:VALENDAR

     files[] = honeypot.test
     ; Information added by Drupal.org packaging script on 2013-12-14
     version = "7.x-1.16"
     ; Information added by Drupal.org packaging script on 2014-05-30
     version = "7.x-1.17"
     core = "7.x"
     project = "honeypot"
     datestamp = "1386996205"
     datestamp = "1401478128"

+      }
+    }
     /**
      * Implements hook_trigger_info().
      */
     function honeypot_trigger_info() {
       return array(
         'honeypot' => array(
           'honeypot_reject' => array(
             'label' => t('Honeypot rejection'),
           ),
         ),
       );
+    }
     /**
      * Implements hook_rules_event_info()
      */
     function honeypot_rules_event_info() {
       return array(
         'honeypot_reject' => array(
           'label' => t('Honeypot rejection'),
           'group' => t('Honeypot'),
           'variables' => array(
             'form_id' => array(
               'type' => 'text',
               'label' => t('Form ID of the form the user was disallowed from submitting.'),
             ),
             // Don't provide 'uid' in context because it is available as
             // site:current-user:uid.
             'type' => array(
               'type' => 'text',
               'label' => t('String indicating the reason the submission was blocked.'),
             ),
           ),
         ),
       );
+    }
     /**
      * Build an array of all the protected forms on the site, by form_id.
+     *
-...
       // If not, throw an error.
       if (time() < ($honeypot_time + $time_limit)) {
         _honeypot_log($form_state['values']['form_id'], 'honeypot_time');
         $time_limit = honeypot_get_time_limit();
         // Get the time limit again, since it increases after first failure.
         $time_limit = honeypot_get_time_limit($form_state['values']);
         $form_state['values']['honeypot_time'] = time();
         form_set_error('', t('There was a problem with your form submission. Please wait @limit seconds and try again.', array('@limit' => $time_limit)));
+      }
-...
           ))->fetchField();
+        }
         // Don't add more than 30 days' worth of extra time.
         $honeypot_time_limit = $honeypot_time_limit + (int) min($honeypot_time_limit + exp($number), 2592000);
         $honeypot_time_limit = (int) min($honeypot_time_limit + exp($number) - 1, 2592000);
         $additions = module_invoke_all('honeypot_time_limit', $honeypot_time_limit, $form_values, $number);
         if (count($additions)) {
           $honeypot_time_limit += array_sum($additions);
-...
       // Allow other modules to react to honeypot rejections.
       module_invoke_all('honeypot_reject', $form_id, $user->uid, $type);
       // Trigger honeypot_reject action.
       if (module_exists('trigger')) {
         $aids = trigger_get_assigned_actions('honeypot_reject');
         $context = array(
           'group' => 'honeypot',
           'hook' => 'honeypot_reject',
           'form_id' => $form_id,
           // Do not provide $user in context because it is available as a global.
           'type' => $type,
         );
         // Honeypot does not act on any specific object.
         $object = NULL;
         actions_do(array_keys($aids), $object, $context);
+      }
       // Trigger rules honeypot_reject event.
       if (module_exists('rules')) {
         rules_invoke_event('honeypot_reject', $form_id, $type);
+      }
+    }

         $this->drupalPost('user/register', $edit, t('Create new account'));
         // Form should have error message.
         $this->assertText(t('There was a problem with your form submission. Please wait'), 'Registration form protected by time limit.');
         $this->assertText(t('There was a problem with your form submission. Please wait 6 seconds and try again.'), 'Registration form protected by time limit.');
+      }
       /**
-...
         $this->assertNoText(t('There was a problem with your form submission.'), 'Honeypot not blocking node form previews.');
+      }
+    }
     /**
      * Test the functionality of the Honeypot module's integration with Trigger.
      */
     class HoneypotTriggerTestCase extends DrupalWebTestCase {
       public static function getInfo() {
         return array(
           'name' => 'Honeypot Trigger integration',
           'description' => 'Ensure that Honeypot triggers events correctly.',
           'group' => 'Form API',
         );
+      }
       public function setUp() {
         // Enable modules required for this test.
         parent::setUp(array('honeypot', 'trigger'));
         // Set up required Honeypot variables.
         variable_set('honeypot_element_name', 'url');
         // Disable time_limit protection.
         variable_set('honeypot_time_limit', 0);
         // Test protecting all forms.
         variable_set('honeypot_protect_all_forms', TRUE);
         variable_set('honeypot_log', FALSE);
         // Set up other required variables.
         variable_set('user_email_verification', TRUE);
         variable_set('user_register', USER_REGISTER_VISITORS);
         // Assign new action to Honeypot form rejection Trigger.
         db_insert('trigger_assignments')
           ->fields(array(
             'hook' => 'honeypot_reject',
             'aid' => 'system_block_ip_action',
             'weight' => 1,
           ))
           ->execute();
+      }
       /**
        * Test trigger integration.
        */
       public function testHoneypotTriggerIntegration() {
         // Set up form and submit it.
         $edit['name'] = $this->randomName();
         $edit['mail'] = $edit['name'] . '@example.com';
         $edit['url'] = 'http://www.example.com/';
         $this->drupalPost('user/register', $edit, t('Create new account'));
         // Make sure Honeypot is working.
         $this->assertText(t('There was a problem with your form submission.'), 'Honeypot working correctly.');
         // Visit the home page and make sure the user is banned.
         $this->drupalGet('node');
         $this->assertText(t('has been banned'), 'User banned successfully.');
+      }
+    }

Projet

Général

Profil

Club Drupal

Révision 55670b15

Ajouté par Assos Assos il y a presque 10 ans