Settings

There are two categories of settings:

Input settings reference

Explore the interactive settings that you can add to your theme.

Sidebar settings reference

Explore the informational settings that you can add to your theme.

你can create settings in the following places:

• config>settings_schema.json
• Section files in thesectionsfolder, using thethe section's{% schema %}tag

Thesettings_schema.jsonfile controls the content of the他们e settingsarea of the theme editor. Settings in this file translate to global theme settings, which can be accessed through the Liquidsettings object.

The section{% schema %}tag is where you can createsection settingsandblock settings. Those settings can be accessed through thesettingsattribute of thesectionobjectandblockobject, respectively.

Settings are defined as a JSONsettingsattribute that's parented to the object that the settings apply to. This attribute accepts an array of settings.

When working with settings, you should familiarize yourself with the following:

• Translating settings
• Accessing setting values
• Checking the setting value format
• Using dynamic sources for settings

你can translatevarious attributesof the settings schema depending on the online store'sactive language. These translations are stored inschema locale files.

Depending on where they were created, you can access settings through the following Liquid objects:

• Theglobalsettingsobject
• Thesectionobject
• Theblockobject

To access a specific setting, append theidattribute of the associated setting to the object that you want to access.

For example, if you had the following setting implemented in each Liquid object:

Then the following Liquid would generate the following output:

When referencing settings, you should always check that the value is in the format that you expect. Any setting without an automatic default value could end up with no value, which translates to an emptystring.

For example, if you have a setting with anidofmessage, then the following Liquid would generate the following output depending on the value:

你can check whether a value is an empty string with theblankoperator. For example:

To avoid an empty string, check that the value is in the format that you expect. It's possible that no resource was selected, selected resource no longer exists, or the selected resource has been hidden.

For example, if you have the followingpagetype setting:

Then you can check for emptiness like the following:

In the past, resource-based settings returned the handle of the associated resource, and you had to access the actual object through Liquid using that handle.

For example, if you had the following product setting, then you would need to access the product object like the following:

Settings for sections included in aJSON templatehave the option for merchants toconnect one or more dynamic sources to the setting, depending on the setting type.

A dynamic source can be either:

• A metafield value
• A resource attribute

Shopify determines the value of each available dynamic source type based on the following:

• The resource associated with the template that the section is in
• The resource settings in the context of the current setting

For example:

The following table lists the available resources and their associated attributes:

The following outlines whichsettingandmetafieldtypes will be compatible:

你can configure a setting's default value to reference a dynamic source. However, only do this if you're rendering a section or block in a context where the dynamic source value exists. For example, don't use a product-related value in a section that:

• Can be rendered in non-product templates

• Doesn't explicitly have aproducttype setting to provide the necessary value

Additional Liquid is invalid when using this method, so you can only reference the value directly. If you include additional Liquid, then you'll get an error.

The following is an example of adefaultsetting that references a dynamic source: