Set_cookie

{% set_cookie %}

Sets a cookie in the HTTP response.

{% set_cookie cookie_name cookie_value attributes %}

{% set_cookie

variable_name

The name of the cookie to set. May be a reference variable

cookie_value

attributes

Key:value pairs with unique keys. May use the variable arguments syntax. Additional directives to use when setting the cookie

attributes

expires

Expiration date/time

path

Cookie path

domain

Cookie domain

secure

True to set the secure flag on the cookie

httponly

True to set the httponly flag on the cookie

There are a small number of reserved and forbidden cookie names, the most prominent being "_mp_permissions" - the name of the cookie used by Marketpath for handling permissions. You must use the {% set_client_permission %} and {% unset_client_permission %} methods to manage permissions instead of manipulating the permissions cookie directly.

Sets the page title.

Sets the meta description for the current page, which is output by default as part of an HTML page's {{ automatic_markup }}.

Saves custom properties on the session. Note that this doesn't mean much unless the user (or the developer) has granted permission for sessions.

Sets the default timezone to use when rendering dates and times on the page that do not already have a separate timezone configured.

Sets the Content-Type header for the HTTP response.

Sets the robots meta directive.

Saves custom properties on the client that will survive across multiple sessions until they are changed, unset, or the "session" permission expires. Note that this doesn't mean much unless the user (or the developer) has granted permission for sessions.

Sets the URL to the favicon for the current page, which is output by default as part of an HTML page's {{ automatic_markup }}.

Saves custom values to predefined profile settings that will be accessible whenever the current profile is logged in. Note that this is meaningless unless the user is logged in. Profile settings may include validation, in which case all settings will be validated before being set and any validation error will prevent the setting(s) from being set. Validation errors may optionally be output to a variable.

Replaces a value on the nearest scope where it has already been defined. If it has not been defined yet, it is stored on the root scope.

Sets one or more headers in the HTTP response.

Defines whether the client has granted or deined permission for a particular feature (eg: sessions). The only permission defined by default is the session permission (configurable in the site properties). However, the template developer may use this mechanism for their own purposes as well. The permissions defined by this method will be stored in the permissions cookie, which may be read and/or modified by client-side javascript.

Sets properties on an editable dictionary object. If the dictionary does not exist it will be created and stored on the current scope. If the dictionary exists but is not editable this will throw an error.

"Unsets" one or more cookies. Because of how cookies work, this will actually ADD the cookie to the response with an expiration date in the past.

Sets the canonical URL for the current page, which is output by default as part of an HTML page's {{ automatic_markup }}.

Sets the HTTP response status code.

Saves custom properties on the profile that will be accessible whenever the current profile is logged in. The properties will be saved to the profile's attribute dictionary. Note that this is meaningless unless the user is logged in.

Examples

{% var expiresDate = "now" | add_minutes: 20 %}
{% set_cookie loginsection "lastsection=accounts" expires:expiresDate path:"/protected" domain:".parentdomain.com" %}

This example demonstrates the use of the expires, path, and domain parameters of the set_cookie method.

{% var sectioncookie = 'accountspage' %}
{% var sectioncount = cookies[sectioncookie] | to_int | plus: 1 %}
{% set_cookie &sectioncookie sectioncount %}

This example demonstrates the use of a reference variable to set a cookie with a dynamic name.

{% if session.allowed and permissions.allow_public_statistics %}
{% capture statisticsString -%}
SessionStart: {{session.start_date | date: 'MMMM dd, yyyy, H:mm:ss'}}
SessionRequests: {{session.num_requests}}
LastRequest: {{request.date | date: 'MMMM dd, yyyy, H:mm:ss'}}
<<Add other custom statistics here>>
{%- endcapture %}
{% set_cookie site_statistics statisticsString %}
{% endif %}

Checks if the "allow_public_statistics" custom permission has been set, and if it has gathers information about the current session statistics for storage in a "site_statistics" cookie - presumably for display using javascript on the site.

Set_cookie

Set_cookie

{% set_cookie %}

Related

Examples