Whether or not the user has visited this URL previously in their current session. Note that this will always be false if the user has not allowed session permission (see the Permissions and Personalization documentation). Using this property prevents the page from being fast-cached
The default output that the calendar produces when output directly to the template. The default output may change at any time. Template developers should avoid using this and should handle the output of calendars themselves
Specific custom fields may be accessed using {{ entity.fieldid }} or {{calendar['field-id']}}
ExampleLoad one calendar and show its title and timezone{% calendar %} loads a single calendar by name or GUID; timezone is the calendar-specific field alongside shared entity properties.
ExampleFetch calendars by filter string and list their titles{% calendars %} returns a calendars list; use filter (and shared list options) to narrow results.
Liquid
{%- calendars var feeds = filter:"Events" limit:25 sort_by:"title" -%}
<ul>
{%- for feed in feeds -%}
<li>{{ feed.linked_title }} ({{ feed.timezone }})</li>
{%- endfor -%}
</ul>
The default output that the calendars will produce when it is output directly to the template - using the "output_in_list" property of each calendar in the items list
List containing all of the combined calendars from the prepended, fetched, and appended lists. If unique is true, this list will not contain any duplicates. If max_size is set, this list will not contain more than the number of calendars specified.
If set, this is the maximum number of items that will be returned in the items list and the maximum number of items that will be included when this calendars object is enumerated as a list. When not set, this value will be 0.
The maximum number of items that were allowed to be in the list of fetched calendars. May be 0 in some cases (such as when when there are no fetched calendars.
The 1-based index of the paginated results returned in the list of fetched calendars, which is calculated from the start and limit parameters. Useful for paginated results.
If any items were fetched from the database, total_pages will contain the number of paginated result pages in the database for the provided arguments. This may also be calculated using the total_count and limit properties.
ExampleFetch calendars by filter string and list their titles{% calendars %} returns a calendars list; use filter (and shared list options) to narrow results.
Liquid
{%- calendars var feeds = filter:"Events" limit:25 sort_by:"title" -%}
<ul>
{%- for feed in feeds -%}
<li>{{ feed.linked_title }} ({{ feed.timezone }})</li>
{%- endfor -%}
</ul>
{% calendar %}
{% calendar output_to_template? [[var, set, or assign]? variable_name]? output_to_template? = value %}Parameters
output_to_templateoptionalflag
Include this flag to write the calendar's output into the page at this point. What that output is differs by type, and for most types it is a built-in default that may change at any time, so see the output property of the calendar object before relying on it. The flag may come before or after the variable name. When the call names no variable, the output is written whether or not the flag is present, which makes {% calendar = value %} the smallest valid use of this method. When the call names a variable, the flag saves the calendar to the variable and writes its output as well.
var, set, or assignoptionalkeyword
Chooses the scope that holds the variable. var, the default, stores it in the current scope. set and assign can store it in outer scopes; Variable Scopes compares the three and when each fits.
variable_nameoptionalvariable
The variable that receives the calendar. It may also be written as a reference, &name, which reads the variable's name from another variable (see Methods Overview). Leave it out to write the calendar to the template instead.
valuerequiredexpression
Required; without a value the method call is not valid. Identifies which calendar to fetch. It can evaluate to the calendar itself, to its GUID, or to other text that identifies it, which for most types is its name; a type identified some other way, or only by GUID, says so in its summary. Names are matched without regard to case, but accented letters must match. A GUID identifies exactly one record, whereas when several records share a name, which of them is returned is not specified, so giving the records you fetch by name unique names avoids the question. A name reads better in a template and a GUID is exact; neither suits every site. When nothing matches, no error is raised: the variable holds an invalid calendar, whose is_valid is false, so check is_valid before using it. When the expression itself has no value, for example an undefined variable, the method does nothing and the variable keeps any earlier value. May use liquid filters.
ExampleLoad one calendar and show its title and timezone{% calendar %} loads a single calendar by name or GUID; timezone is the calendar-specific field alongside shared entity properties.
Include this flag to write the calendars list's output into the page here. That output is a built-in default for most types and may change at any time, so see the output property of the calendars object before relying on it. The flag may come before or after the variable name. With no variable named, the output is written whether or not the flag is present; with one, the flag saves the list and writes its output too.
var, set, or assignoptionalkeyword
Chooses the scope that holds the variable. var, the default, stores it in the current scope. set and assign can store it in outer scopes; Variable Scopes compares the three and when each fits.
variable_nameoptionalvariable
The variable that receives the calendars list. It may also be written as a reference, &name, which reads the variable's name from another variable (see Methods Overview). Leave it out to write the list to the template instead.
argumentsrequiredcollection
Key:value pairs. May use the variable arguments syntax. Written after a required =. The name:value pairs choose which calendars to fetch and how to narrow, order and page them. Nothing is fetched unless the call gives an argument other than prepend, append, unique, exclude_prepended, exclude_appended, max_size and cache_random; without one, the list holds only the prepended and appended calendars.
Options
prependoptionallist
May be a single calendar, a list of calendars, or the name or guid of one calendar, to be included at the beginning of the calendars list.
appendoptionallist
May be a single calendar, a list of calendars, or the name or guid of one calendar, to be included at the end of the calendars list.
excludeoptionallist
May be a single calendar, a list of calendars, or the name or guid of one calendar that should NOT be included in the fetched results. Has no effect on prepended or appended calendars.
exclude_prependedoptionalboolean
True to specifically exclude all prepended calendars from the fetched results. If "unique:true" is specified this is the default behavior, although you may also specify "exclude_prepended:false" to allow any prepended items to be fetched along with other results anyway.
exclude_appendedoptionalboolean
True to specifically exclude all appended calendars from the fetched results. This is false by default - even if "unique:true" is specified - so that results are returned in the proper order.
uniqueoptionalboolean
True to remove duplicates from each of the resulting lists (prepended, fetched, appended, and items), although there may be duplicates between the prepended, fetched, and appended lists. The "items" list will include objects in the order in which they appear - with prepended items first, then fetched items, then appended items.
max_sizeoptionalinteger
The maximum number of items to be included in the "items" list. If there are any prepended or appended items, this will automatically lower the "limit" to only fetch as many calendars as needed. Note that this may also impact both the "page" and "total_pages" values in the resulting calendars. In order to use pagination with a list loaded using "max_size" use "start" instead of "page" and "limit".
filteroptionalvalue
Only include calendars that match the given string filter
folderoptionalvalue
May include multiple folders. Only include calendars with one of the given folders
date_created_startoptionalvalue
Only include calendars with date_created greater than or equal to date_created_start. Remember that date_created will typically be the date that the calendar was first published.
date_created_endoptionalvalue
Only include calendars with date_created less than or equal to date_created_end. Remember that date_created will typically be the date that the calendar was first published.
has_urloptionalboolean
If true, only return calendars that have a URL. If false, only return calendars that do NOT have a URL.
templateoptionalobject
Only return calendars with one of these templates. May be a single template, a list of templates, or the name or guid of a template to filter the results by. A template name is its path from the root, with or without the leading /; unlike {% template %}, a list method does not accept a relative path.
include_in_searchoptionalboolean
True or false to only return calendars whose include_in_search property matches the provided value.
domain_nameoptionalobject
Only return calendars from the given domain.
startoptionalinteger
Set the 1-based index of the first calendar to fetch.
pageoptionalinteger
Used to automatically calculate the first calendar to fetch based on both the "limit" and the 1-based "page" value. Defaults to 1, but is ignored if "start" is set.
limitoptionalinteger
The maximum number of calendars to fetch. Defaults to 10; a value that is not a number also gives 10. The largest limit is 1000, and a limit of 0 or less, or above 1000, returns up to 1000 calendars. Note that if "max_size" is defined, then "limit" may be automatically lowered even if specified separately.
sort_byoptionalstring
Specify which property to sort the results by. Has no effect on prepended or appended calendars. An unrecognized value is ignored without an error and the default order is used. Some methods accept more values than the built-ins listed here; see each method. By default, results will be sorted by relevance if there is a filter string and date_created desc (newest first) if not. Options include:
relevance: only applies when there is a filter string. sort_direction applies: descending, the default, puts the best match first.
date_created: the date each calendar was first published. Unpublishing and republishing one resets date_created to the current date.
random: results will be returned in a random order, which prevents the page from being fast-cached. Setting cache_random:true overrides this behavior and allows the page to be fast-cached anyway.
name
title
url
browser_title
sort_directionoptionalstring
asc or desc. Defaults to desc; any value other than asc sorts descending.
cache_randomoptionalboolean
True to allow the results to be cached when sort_by is "random".
ExampleFetch calendars by filter string and list their titles{% calendars %} returns a calendars list; use filter (and shared list options) to narrow results.
Liquid
{%- calendars var feeds = filter:"Events" limit:25 sort_by:"title" -%}
<ul>
{%- for feed in feeds -%}
<li>{{ feed.linked_title }} ({{ feed.timezone }})</li>
{%- endfor -%}
</ul>