Skip to content

Meta Properties

Meta properties can extend content, containers and compose channels in custom content. Content and container meta properties are defined in CEO's config files, as they can impact multiple facets. Custom content channel meta properties are managed directly in CEO.

You can also use a changing meta property value to trigger an Automation.

Basic Properties

Text

Basic single line text input with unformatted text.

Examples

  • Titles
  • Names
  • Button labels

Template Usage

{{ entry.myTextInput }}

Text Area

Basic multi-line text input with unformatted text.

Examples

  • Basic descriptions
  • Simple raw text

Template Usage

{{ entry.myTextArea }}

Checkbox

Single on/off or true/false option.

Examples

  • Published status
  • Featured status

Template Usage

{% if entry.myCheckbox %}
    ...
{% endif %}

Rich Text

Formatted text with standard rich formatting options. This is the "Basic Editor" CEO feature, not the more advanced "Article Editor," which is currently not available as a meta property.

Examples

  • Content text
  • Descriptor text

Template Usage

{{ entry.myRichText|raw }}

Date

Single date value, encodes day, month, and year only. Dates are standard DateTime objects, so they can be treated as strings or manipulated with date functions.

Examples

  • Published times
  • Event dates

Template Usage

{{ entry.myDate }}
{{ entry.myDate|date('F d, Y') }}

Date Time

Single date and time value, encodes day, month, year, hour, minute and seconds. Dates are stored as UTF and converted on the front end to the local timezone. Dates are standard DateTime objects, so they can be treated as strings or manipulated with date functions.

Examples

  • Published times
  • Event times

Template Usage

{{ entry.myDate }}
{{ entry.myDate|date('F d, Y g:ia') }}

Fields that are either programmatically added or manged in the CEO Connect edit flow.

Examples

  • Print headline
  • Import meta data

Template Usage

None

Advanced Properties

Editor Text

Unformatted, raw text or embed codes. Editor text is not formatted or otherwise altered when saved, beyond standard filtering.

Examples

  • Embed code
  • Raw javascript

Template Usage

{{ entry.myEditorText }}

File

A single file upload option. File meta property items are not managed as CEO media and are only available via the entry. If you require standard CEO media, use "Related Content."

Examples

  • Head shots
  • Ad images

Template Usage

{{ entry.myFile }}
{{ entry.myFile|transform({'w': 400, 'ar': '1:1'}) }}

Related Content

Multiple CEO content items, can be any content type in CEO including articles, pages, and all media. Regardless of the number of selected items, this will always be presented as an array.

Examples

  • Special section articles
  • Galleries

Template Usage

{% for item in entry.myRelatedContent %}
    {{ item.title }}
    {{ item.customUrl({'w': 1000}) }}
{% endfor %}

Select Entry

Select a single entry from an associated channel. Associated channel is fixed and defined in the channel edit screen.

Examples

  • Classified ad category
  • Special section

Template Usage

{{ entry.myRelatedEntry.title }}
{{ entry.myRelatedEntry.myRelatedEntryField }}

Select Entries

Select multiple entries from an associated channel. Like the single Select Entry above, it is defined in the channel edit screen.

Examples

  • Associated categories
  • Related content

Template Usage

{% for item in entry.mySelectedEntries %}
    {{ item.myEntryField }}
{% endfor %}

Secure Text

Basic encrypted text. Text is encrypted with the site's entropy key. While the text is strongly encrypted, the key is general use per site. You should not store confidential information in this field. Essentially, this encrypts the string at rest.

Examples

  • Wiki password
  • API keys

Warning

The field is decrypted on display, so calling {{ entry.mySecureField }} will display the plain text value.

JSON Text

JSON encoded text, similar to the editor text, except this text is validated as JSON data and treated as such.

Examples

  • Configuration options
  • Encoded data

Template Usage

{{ entry.myJsonField.someKey }}
{{ entry.myJsonField[0]['someKey'] }}