Skip to documentation content

Folder

On this page

    Using folders to organize content by type or by cross-type grouping (e.g. by company).

    Folders are a means of grouping like objects together within CMS. These can be used for specific types of objects only, such as with images, or can be used across multiple object types. For example, grouping images and articles for "Company A" into one folder and other images and articles for "Company B" into a separate folder.

    {{ folder }}

    Properties
    Name Type Description
    object_type string Will always be folder
    is_valid boolean True if this references a published folder
    guid string The unique identifier for this folder
    value string Synonym for guid
    name {{ text }} The name of the folder
    title {{ text }} The title of the folder
    linked_title string A link to the folder if it has a URL, or the escaped title if not
    sub_folders {{ folders }} A list containing all of the child folders of the current folder
    has_url boolean True if the folder has a URL
    include_in_search boolean Whether or not this folder should be returned in on-site search results
    domain_name {{ text }} The domain name used by the URL for this folder
    url {{ text }} The portion of the URL for this folder following the domain name
    full_url string The full URL for this folder including the scheme, domain name, and path
    visited boolean 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
    template_guid string The unique identifier for the template that would be used to respond to this URL
    template {{ template }} The template that would be used to respond to this URL
    canonical_url {{ url }} The canonical URL if this is not the original source of content for this URL
    browser_title {{ text }} The browser title for this URL. The editor requires a browser title for every entity that has a URL.
    meta_description {{ textarea }} The meta description for this URL
    meta_robots {{ text }} The meta robots for this URL
    keywords {{ textarea }} The SEO keywords for this URL
    search_entity_guid string The unique identifier for the entity that search results should be directed to (if this folder does not have a URL)
    search_entity {{ entity }} The entity that search results should be directed to (if this folder does not have a URL)
    folder_guid string The unique identifier for the folder that contains this folder.
    folder {{ folder }} The folder that contains this folder.
    field_id string The identifier for this field
    label string The label for this field
    output string The default output that the folder 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 folders themselves
    data {{ data }} Object containing the custom fields on this folder
    * string Specific custom fields may be accessed using {{ entity.fieldid }} or {{folder['field-id']}}
    Example Load one folder and walk its sub_folders list{% folder %} loads a single folder by path or GUID; sub_folders is the list of its child folders.
    Liquid
    {%- folder var library = "Media Library" -%}
{%- if library.is_valid -%}
	<h2>{{ library.title }}</h2>
	<ul>
	{%- for child in library.sub_folders -%}
		<li>{{ child.linked_title }}</li>
	{%- endfor -%}
	</ul>
{%- endif -%}

    {% folder %} fetches a single folder. Pass the path of the folder (for a top-level folder, its name) or its GUID after the assignment target. The folder-specific sub_folders property is a folders list of direct children; shared entity properties such as title, linked_title, and is_valid are also available.

    Example Fetch folders by filter string and list their titles{% folders %} returns a folders list; use filter (and shared list options) to narrow results, then read each folder's title.
    Liquid
    {%- folders var sections = filter:"Company" limit:25 sort_by:"title" -%}
<ul>
{%- for section in sections -%}
	<li>{{ section.linked_title }} ({{ section.sub_folders.size }} subfolders)</li>
{%- endfor -%}
</ul>

    {% folders %} is the list method for folder entities. The filter option keeps folders whose text matches the given string; combine it with shared list options such as limit and sort_by. Iterate the resulting folders object directly. Each folder still exposes sub_folders for drilling into children.

    {{ folders }}

    Contains multiple folders.

    Properties
    Name Type Description
    object_type string Will always be folders
    is_valid boolean True if this contains at least one published folder
    output string The default output that the folders will produce when it is output directly to the template - using the "output_in_list" property of each folder in the items list
    prepended list List containing any prepended folders.
    fetched list List containing all of the folders that were fetched from the database (as opposed to prepended or appended).
    appended list List containing any appended folders.
    appended_unique list List containing any appended folders excluding any folders that are in either the list of prepended or fetched folders.
    items list List containing all of the combined folders 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 folders specified.
    size integer The total number of folders in the items list, including prepended, fetched, and appended lists, and respecting the unique and max_size properties.
    max_size integer 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 folders object is enumerated as a list. When not set, this value will be 0.
    unique boolean When true, the items list will not contain any duplicates. Only the first instance of each folder will be included.
    limit integer The maximum number of items that were allowed to be in the list of fetched folders. May be 0 in some cases (such as when when there are no fetched folders.
    start integer The 1-based index of the first item in the list of fetched folders.
    page integer The 1-based index of the paginated results returned in the list of fetched folders, which is calculated from the start and limit parameters. Useful for paginated results.
    total_count integer The 1-based index of the first item in the list of fetched folders
    total_pages integer 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.
    Example Load one folder and walk its sub_folders list{% folder %} loads a single folder by path or GUID; sub_folders is the list of its child folders.
    Liquid
    {%- folder var library = "Media Library" -%}
{%- if library.is_valid -%}
	<h2>{{ library.title }}</h2>
	<ul>
	{%- for child in library.sub_folders -%}
		<li>{{ child.linked_title }}</li>
	{%- endfor -%}
	</ul>
{%- endif -%}

    {% folder %} fetches a single folder. Pass the path of the folder (for a top-level folder, its name) or its GUID after the assignment target. The folder-specific sub_folders property is a folders list of direct children; shared entity properties such as title, linked_title, and is_valid are also available.

    Example Fetch folders by filter string and list their titles{% folders %} returns a folders list; use filter (and shared list options) to narrow results, then read each folder's title.
    Liquid
    {%- folders var sections = filter:"Company" limit:25 sort_by:"title" -%}
<ul>
{%- for section in sections -%}
	<li>{{ section.linked_title }} ({{ section.sub_folders.size }} subfolders)</li>
{%- endfor -%}
</ul>

    {% folders %} is the list method for folder entities. The filter option keeps folders whose text matches the given string; combine it with shared list options such as limit and sort_by. Iterate the resulting folders object directly. Each folder still exposes sub_folders for drilling into children.

    {% folder %}

    Identifies the folder by its path: the names of the folders from a top-level folder down, separated by /. If two folders at the same level of the path share a name, the path does not resolve.

    {% folder output_to_template? [[var, set, or assign]? variable_name]? output_to_template? = value %}
    Parameters
    output_to_template optionalflag
    Include this flag to write the folder'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 folder 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 {% folder = value %} the smallest valid use of this method. When the call names a variable, the flag saves the folder to the variable and writes its output as well.
    var, set, or assign optionalkeyword
    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_name optionalvariable
    The variable that receives the folder. 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 folder to the template instead.
    value requiredexpression
    Required; without a value the method call is not valid. Identifies which folder to fetch. It can evaluate to the folder 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 folder, 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.

    Fetches a single {{ folder }}.

    Example Load one folder and walk its sub_folders list{% folder %} loads a single folder by path or GUID; sub_folders is the list of its child folders.
    Liquid
    {%- folder var library = "Media Library" -%}
{%- if library.is_valid -%}
	<h2>{{ library.title }}</h2>
	<ul>
	{%- for child in library.sub_folders -%}
		<li>{{ child.linked_title }}</li>
	{%- endfor -%}
	</ul>
{%- endif -%}

    {% folder %} fetches a single folder. Pass the path of the folder (for a top-level folder, its name) or its GUID after the assignment target. The folder-specific sub_folders property is a folders list of direct children; shared entity properties such as title, linked_title, and is_valid are also available.

    {% folders %}

    The prepend, append and exclude arguments identify a folder the way {% folder %} does, by its path or by its GUID.

    {% folders output_to_template? [[var, set, or assign]? variable_name]? output_to_template? = arguments %}
    Parameters
    output_to_template optionalflag
    Include this flag to write the folders 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 folders 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 assign optionalkeyword
    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_name optionalvariable
    The variable that receives the folders 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.
    arguments requiredcollection
    Key:value pairs. May use the variable arguments syntax. Written after a required =. The name:value pairs choose which folders 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 folders.

    Options

    prepend optionallist
    May be a single folder, a list of folders, or the name or guid of one folder, to be included at the beginning of the folders list.
    append optionallist
    May be a single folder, a list of folders, or the name or guid of one folder, to be included at the end of the folders list.
    exclude optionallist
    May be a single folder, a list of folders, or the name or guid of one folder that should NOT be included in the fetched results. Has no effect on prepended or appended folders.
    exclude_prepended optionalboolean
    True to specifically exclude all prepended folders 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_appended optionalboolean
    True to specifically exclude all appended folders from the fetched results. This is false by default - even if "unique:true" is specified - so that results are returned in the proper order.
    unique optionalboolean
    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_size optionalinteger
    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 folders as needed. Note that this may also impact both the "page" and "total_pages" values in the resulting folders. In order to use pagination with a list loaded using "max_size" use "start" instead of "page" and "limit".
    filter optionalvalue
    Only include folders that match the given string filter
    folder optionalvalue
    May include multiple folders. Only include folders that are immediate children of one of the given folders
    date_created_start optionalvalue
    Only include folders with date_created greater than or equal to date_created_start. Remember that date_created will typically be the date that the folder was first published.
    date_created_end optionalvalue
    Only include folders with date_created less than or equal to date_created_end. Remember that date_created will typically be the date that the folder was first published.
    has_url optionalboolean
    If true, only return folders that have a URL. If false, only return folders that do NOT have a URL.
    template optionalobject
    Only return folders 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_search optionalboolean
    True or false to only return folders whose include_in_search property matches the provided value.
    domain_name optionalobject
    Only return folders from the given domain.
    start optionalinteger
    Set the 1-based index of the first folder to fetch.
    page optionalinteger
    Used to automatically calculate the first folder to fetch based on both the "limit" and the 1-based "page" value. Defaults to 1, but is ignored if "start" is set.
    limit optionalinteger
    The maximum number of folders 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 folders. Note that if "max_size" is defined, then "limit" may be automatically lowered even if specified separately.
    sort_by optionalstring
    Specify which property to sort the results by. Has no effect on prepended or appended folders. 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 folder 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_direction optionalstring
    asc or desc. Defaults to desc; any value other than asc sorts descending.
    cache_random optionalboolean
    True to allow the results to be cached when sort_by is "random".

    Fetches a list of {{ folders }}.

    Example Fetch folders by filter string and list their titles{% folders %} returns a folders list; use filter (and shared list options) to narrow results, then read each folder's title.
    Liquid
    {%- folders var sections = filter:"Company" limit:25 sort_by:"title" -%}
<ul>
{%- for section in sections -%}
	<li>{{ section.linked_title }} ({{ section.sub_folders.size }} subfolders)</li>
{%- endfor -%}
</ul>

    {% folders %} is the list method for folder entities. The filter option keeps folders whose text matches the given string; combine it with shared list options such as limit and sort_by. Iterate the resulting folders object directly. Each folder still exposes sub_folders for drilling into children.