Marketpath CMS Developer Tutorial Series

Entities

Last Updated 3/6/2018

Most information in the CMS is stored in entities. There are many different types of entities and many ways to add and access data associated with entities, which makes it a topic of primary significance to fully understand for any CMS developer.

First a definition is in order. In the CMS, an entity is any object from which a user can create a page or URL. This includes objects such as articles, authors, blogs, blog posts, calendars, calendar entries, datastores, datastore items, folders, galleries, and tags. This does NOT include menus, redirects, snippets, templates, javascript, or stylesheets.

Entities are not required to have a page. They may be used for other purposes - such as for selection in custom fields or to query directly from the template into a list. There are three main ways that entities may be queried:

  1. Urls: Every page (URL) has an entity associated with it, and so the page is the primary way that entities are loaded by the CMS. In page templates the keyword entity is used to 
     
  2. Templates: The template developer can query entities using our templating engine in a variety of ways. Entities pulled in this way may or may not have urls.
  3. Custom fields: A developer can create custom fields (or datastores or custom site settings) that reference entities. These may be defined in as many ways as the developer can query the templating engine, and have roughly the same limitations.

Regardless of how entities are queried, they always have the same structured and unstructured data available.

---- End of Lesson ----

Question? Correction?

Let's work together to make our documentation as helpful as possible.

What is your name? 
What is your email address? 
Feedback: