1
|
Creates calendar displays of Views results.
|
2
|
|
3
|
Create a new calendar by using the calendar template for the desired
|
4
|
date field. See a link to create a view from a template at the top
|
5
|
of the Views listing page.
|
6
|
|
7
|
If the Calendar iCal module is enabled, an iCal feed can be
|
8
|
attached to the view.
|
9
|
|
10
|
For a quick and easy start, install the Date Tools module, then use
|
11
|
the Date Tools Wizard to create a content type with a date field
|
12
|
and a calendar that displays that field, all in a single step!
|
13
|
|
14
|
|
15
|
=========================================================
|
16
|
CACHING & PERFORMANCE
|
17
|
=========================================================
|
18
|
|
19
|
Calendars are very time-consuming to process, so caching is recommended.
|
20
|
You can set up caching options for your calendar in the Advanced section
|
21
|
of the View settings. Even setting a lifetime of 1 hour will provide some
|
22
|
benefits if you can live with a calendar that is 1 hour out of date.
|
23
|
Set the lifetime to the longest value possible. You will need to clear
|
24
|
the caches manually or using custom code if the content of the calendar
|
25
|
changes before the cache lifetime expires.
|
26
|
|
27
|
The recommended settings for time-based caching are:
|
28
|
|
29
|
- Query results
|
30
|
Cache the query only when not using ajax. Do not cache the query
|
31
|
on any display that uses ajax for its results.
|
32
|
|
33
|
- Rendered output:
|
34
|
Always try to cache rendered output. Rendering the output is the most
|
35
|
time-consuming part of building a calendar. This is especially
|
36
|
important for the Year view, less important for the Day view.
|
37
|
|
38
|
As with all caching options, please test to be sure that caching
|
39
|
is working as desired.
|
40
|
|
41
|
If performance is a problem, or you have a lot of items in the calendar,
|
42
|
you may want to remove the Year view completely.
|