{"id":252736,"date":"2020-12-24T11:21:23","date_gmt":"2020-12-24T11:21:23","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=252736"},"modified":"2026-07-31T04:38:57","modified_gmt":"2026-07-31T04:38:57","slug":"class-setting-in-pimcore","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/class-setting-in-pimcore\/","title":{"rendered":"Class Setting in Pimcore"},"content":{"rendered":"

Every Pimcore class carries a set of options that shape how its objects behave. This guide covers Class Setting in Pimcore for the latest Studio.<\/p>\n

You already know how to create a class and a data object<\/a>. This post goes one layer deeper into the class options themselves.<\/p>\n

We target Pimcore 12 (Platform 2026.1). Screens, paths, and labels all match the modern React-based Pimcore Studio.<\/p>\n

One heads-up before you start. The legacy ExtJS “classic” admin no longer ships in 2026.1, so the old “Settings > Data Objects > Classes” route is gone.<\/p>\n

Where Class Setting in Pimcore lives now<\/h2>\n

Every class option sits on the class definition, inside Studio. You reach it through the left navigation.<\/p>\n

Follow this exact path:<\/p>\n

    \n
  1. Open Data Management<\/strong> in the left navigation.<\/li>\n
  2. Expand Data Model Definitions<\/strong>.<\/li>\n
  3. Click Classes<\/strong>, then open your class.<\/li>\n<\/ol>\n
    \"pimcore-class-setting-studio-classes-menu\"<\/figure>\n

    You will see siblings next to Classes<\/strong>. These include Field Collections, Object Bricks, Classification Store, Select Options, Quantity Values, Bulk Export, and Bulk Import.<\/p>\n

    Open any class and you land on its General<\/strong> tab. That tab is where Class Setting in Pimcore begins.<\/p>\n

    The General tab at a glance<\/h2>\n

    The General<\/strong> tab holds the class-wide options. Each option here is one piece of Class Setting in Pimcore, and it controls behavior, not the individual fields.<\/p>\n

    \"pimcore-class-setting-general-tab\"<\/figure>\n

    A first-timer only touches a few of these. The rest stay at their defaults until a model needs them.<\/p>\n

    The sections below walk each important option in turn. Each maps to one real property on the class definition.<\/p>\n

    Parent PHP Class<\/h2>\n

    Every Pimcore class is a PHP class under the hood. By default it extends Pimcore\\Model\\DataObject\\Concrete<\/code>.<\/p>\n

    The Parent Class<\/strong> field lets you change that base. Point it at your own PHP class to share methods and logic across several classes.<\/p>\n

    \"pimcore-class-setting-parent-php-class\"<\/figure>\n

    Leave this field empty for a normal class. Pimcore then generates a model that extends Concrete<\/code>, and you get every standard object method for free.<\/p>\n

    Keep one distinction clear. Parent Class is PHP code inheritance, not the object value inheritance in the next section.<\/p>\n

    Allow Inheritance<\/h2>\n

    Allow Inheritance<\/strong> is the class option most teams reach for first. It is off by default.<\/p>\n

    Turn it on and a child object inherits any unset field value from its parent object. Pimcore walks up the tree to the nearest parent of the same class.<\/p>\n

    \"pimcore-class-setting-allow-inheritance\"<\/figure>\n

    Picture a clothing catalog. A parent “Shirt” object holds shared values like brand and material.<\/p>\n

    Child objects under it override only what differs, such as size or color. The children inherit everything else from the parent, so you never retype shared data.<\/p>\n

    This inheritance also flows through variants. A variant inherits from its parent object exactly the same way, as long as both share the class.<\/p>\n

    Variants: Allow Variants and Show Variants<\/h2>\n

    A variant is a special object that models a variation of a product. Think one shirt in red, blue, and green.<\/p>\n

    Two separate options on the General tab govern variants. Both start switched off.<\/p>\n

    \"pimcore-class-setting-variants\"<\/figure>\n

    Allow Variants<\/strong> enables variant children on the class. Only then can an object of this class hold variants beneath it.<\/p>\n

    Show Variants<\/strong> is a display option, not a data option. It controls how variant objects surface in the object tree, separate from whether the class permits them.<\/p>\n

    Under the hood, a variant is just an object with the type variant<\/code>. It sits below a parent object of the same class and pairs naturally with Allow Inheritance.<\/p>\n

    Custom icon for a class<\/h2>\n

    A custom icon makes a class easy to spot in the tree. Set it once on the class and every object of that class shows it.<\/p>\n

    The Icon<\/strong> field on the General tab opens an icon selector. You can search the built-in icon sets or point to a custom icon path.<\/p>\n

    \"pimcore-class-setting-custom-icon\"<\/figure>\n

    One change from older Pimcore is worth noting. In Pimcore 12 the icon is a class-level option, so there is no separate per-object icon field.<\/p>\n

    Custom layouts<\/h2>\n

    A custom layout is an alternative view of the same class. The data stays identical, but the field arrangement changes per audience.<\/p>\n

    Use custom layouts to show a lean set of fields to one team and the full set to another. You configure them right inside the class editor.<\/p>\n

    \"pimcore-class-setting-custom-layout\"<\/figure>\n

    Each custom layout takes a name and an optional description. You can flag one as the default layout for the class.<\/p>\n

    Studio also respects permissions here. Non-admin users only see the custom layouts their role allows, so you can tailor the editor per team.<\/p>\n

    Other class settings in Pimcore worth knowing<\/h2>\n

    A handful of remaining options round out Class Setting in Pimcore. You will not need them on day one, but they matter as models grow.<\/p>\n