Configure Site Date and Time
- Navigate to admin/config/regional/date-time
Enable The Necessary Modules
- Date All Day
- Date API
- Date Popup
- Date Repeat API
- Date Repeat Field
- Date Tools
- Date Views
Configure A Repeating Date Field
Make sure you have at least one date field configured to handle repeating dates.
Under MORE SETTINGS AND VALUES > DATE ENTRY configure the following:
- Set Date entry options to a format that is easy to read. For example, something that has AM and PM
- Enable Display all day checkbox
Under the FIELD SETTINGS configure the following:
Under Date attributes to collect enable the following
- Year, Month, Day, Hour and Minute
- Enable Collect an end date
- Under Repeating date select Yes
Make Sure You're Entering Your Dates Correctly
It's easy to enter the dates incorrectly, which in turn makes repeating dates display incorrectly.
Make sure your End Date reflects the the time your event ends. So, if you have a repeating date that starts at 12:00pm and ends at 12:30pm, make sure this is reflected in the end date. The date itself should be the same
Use the Repeat rule to actually add the date the event ends.
Correctly Display Repeating Dates In Views
You'll notice that if you create a view that displays repeating dates, the view can become overwhelming quickly as demonstrated below.
For example, if the event repeats 11 times, the view will display 11 instances of the event while still displaying all repeating dates that have occurred.
Limit View To Only Show Upcoming Repeating Dates
The first thing we'll want to do is limit the view to only show upcoming repeating events, and not ones that have already occurred. For example, I'm writing this on February 17th, 2016 and my repeating event started on February 3rd, 2016. In the image above, there are 11 instances of the event (one for each repeating date). However, since 3 instance of this event are over, the view should only display 8 instances.
In order to limit a view to only show upcoming repeating events, make sure you're displaying your data as fields, and not as content such as teasers.
- Under FILTER CRITERIA search for Date: Date (node) (note this this is different than the date field in your node)
- For Date selection form element, Filter granularity and ** Starting year** you can use the default settings
- Under Date field(s) find the date field you are using in your nodes, and specifically select the start date value
- For Method select OR
- On the next page, select Is greater than or equal to for the Operator
- Enter a relative date and use 12AM today as the relative date
Display Each Repeating Date In Its Own Row
Even though we've limited our view to only show upcoming repeating dates, it's still very cluttered. Each row of a repeating date still shows all instances of that repeating date. What we want to do is show each instance in its own row.
The image on the left is what we currently have configured. The image on the right is what we're looking to achieve.
- Edit your date field in the view we created in the previous steps. Under MULTIPLE FIELD SETTINGS deselect Display all values in the same row
Correctly Display Repeating Dates Using Relative Start Date
By default, a repeating date will display all instances on the node display as demonstrated below. This creates a cluttered display, and is also not helpful once an instance is over.
Luckily there is a patch that supports relative date formats in the filter of the date field output formatter.
- Using the command line, navigate to the date module directory.
- Apply the patch. I am on a Mac, so I use the following code when applying patches.
wget https://www.drupal.org/files/date-allow-relative-dates-for-output-filter.patchpatch -p1 < date-allow-relative-dates-for-output-filter.patchrm date-allow-relative-dates-for-output-filter.patch
Navigate to the default display for your content type that has a date field.
- Under starting from enter now
- Select Use php relative dates notation
- Click Update then Save
I'm writing this section on February 18th, 2016. So, my event that repeates from February 3rd, 2016 - April 19th, 2016 will now only show instances that have yet to occur.