Template objects

When working with templates the system creates objects that you can use depending on what context you are in.

Let’s assume you are working with the product template product.liquid (in a ‘product context’), when using that template you have access to the current product object and you can inspect it using {{ product | print_r}}.

Some objects are always available (but lazy loaded on access) such as collections and products but there’s also a customer object which only exists when a customer has logged in.

These objects are made available server side when using liquid code but can be made available client side js using the json filter const p = {{ product | json}};.

{% comment %}
   We can reference a product object since we are in a product context.
{% endcomment %}

{% assign productTitle = product.title | upcase %}
{% assign onSale = false %}
{% if product.compareAtPrice > product.price %}
   {% assign onSale = true %}
{% endif %}

{{productTitle}} is {% unless onSale %}not {% endunless %}on sale! 

Global objects

There are global objects that can be reached from all contexts.

CMS

eCommerce

Site object {{ site }}

You can always print the site object with {{ site | print_r }}

Request object {{ request }}

The request object will specify the host, origin, path, query, referer and scheme of the current request.

Using the request information, it is possible to add in user-specific content, for example, if the referer contains “google” the content can be rendered adapted to this.

{% if request.referer contains "google" %}
	<aside>
		<div class="promo brand">
				<h2>Want to create websites?</h2>
				<a class="shiny-cta" href="/features">Learn more</a>
		</div>
	</aside>
{% endif %}

Cart object

{{ cart }}

Context dependent objects

Context dependent objects, the name of the object is the same as the current context i.e. page,product, cart, collection.

CMS

Page object

| id | Page id | | authorId | Author id | | author | Author | | published | Published date | | createdAt | First created | | updatedAt | Latest update date | | publishAt | Publish date | | lang | Language | | handle | Editable page handle | | title | Page title | | html | Page content in html-format | | meta | H1 and meta data: Title, description, keywords and data | | image | Page image with source, and alt texts | | text | Page-content in text format | | format | Editor format | Table: Page object properties

eCommerce

Example

In the page.liquid template the object {{ page }} exists and contains fields such as {{ page.html }} which provides all the content or {{ page.createdAt }} for creation date.

To view all the fields the filter | print_r can be used.

Referencing outside the context

It is possible to reach the objects outside the context of the object.

pages, blogs, collections, products combined with a reference to theme settings, handle/id or an position in the array will extract an object (page, blog, collection or product).

Using reference to theme settings

With settings it is possible to reach a specific blog/collection/product/page/article from the theme settings data stored in the settings object.

{% assign collection = collections[settings.homepageCollection] %}

Using handle privacy

{{ pages['privacy'].html }}

Referencing a product from products

The products object will contain all the products in an array, it is possible to pick a product from the array by specifying the position, with 0 being the first. products[0] will pick the first product.