Basker Docs

Custom object instances

Create individual instances of a custom object you have defined, and manage them like any other content

Once you have defined a custom object, the entries you create from it are called instances. If you have defined a "Sponsor" object, each sponsor you add is a Sponsor instance. The object definition fixes the structure. You complete the content of each instance.

Creating an instance

Open the custom object's admin area. The list shows every instance you have created. Add a new instance. Complete the fields the object defines.

Each instance has a title you enter, plus the fields the object defines. The title identifies the instance in lists and pickers, and must be unique among instances of that object. Instances save directly. They do not have separate draft and published states or version history, and their fields are not translated per language.

Referencing an instance from other content

Custom object instances can be referenced from any relationship field that points at the object. Add a "Sponsors" relationship attribute on events, and each event editor gains a picker for choosing sponsor instances.

The same instance can be referenced from as many places as you need. Updating the instance updates it everywhere it is used.

Listing instances on your site

Whether and how custom object instances appear on the live site depends on your theme. If the theme provides blocks that render the object (for example, a "Sponsor wall" block), those blocks show the instances you have created. If the theme does not, instances stay internal and only appear through fields they are referenced from.

Smart collections do not currently list custom object instances directly. If you need a dynamic public listing, add the data to a supported content type such as organizations, people, or events, or ask your theme developer to build the listing from the custom object data.

Where to go next

On this page