Frontend Adapters

Every entry in the adapter mapping pairs a frontend adapter with a backend adapter. The frontend adapter decides which input controls the Tree Levels tab renders for that data type; the backend adapter resolves the value used to build the tree.

Pimcore Studio ships four frontend adapters, and the frontend key must name one of them:

Frontend adapter	Renders
SimpleValueAdapter	No additional controls; the field value is used as-is.
LocalizedFieldAdapter	A language selector.
RelationAdapter	A target class and field selector, or a Symfony expression.
ObjectBrickAdapter	An object brick and brick field selector.

pimcore_backend_power_tools:
  pimcore_alternative_object_trees:
    adapters:
      input: #= the datatype of the corresponding class field
        frontend: SimpleValueAdapter
        backend: App\Adapter\AlternativeElementTree\CustomAdapter

info

Custom frontend adapters are not an extension point in Pimcore Studio. The four adapters above are a closed set. Extend the tree by writing a custom backend adapter and pairing it with whichever frontend adapter renders the controls your data type needs.

Earlier versions allowed registering custom ExtJS frontend adapters through the Admin Classic UI. That mechanism was removed together with Admin Classic.