Upgrade Notes
Upgrade to 2026.4.0
GraphQL
- Added the
focalPointsfield to the asset type. For images with a focal point set in the asset editor it returns{x, y}as percentages (Float,0–100) of the image width/height, read from the asset'sfocalPointX/focalPointYcustom settings; it isnullfor images without a focal point and for all other asset types. This is a purely additive schema change; existing queries are not affected. - The result messages of denied create mutations now name the requested parent, e.g.
not allowed to create object Car in parent path '/shop'or... in parent id 5(create object, asset, document and object/asset/document folder). The create-folder messages (not allowed to create assetfolder, ...) also lost their trailing space. Clients that compare these messages exactly need to adjust. - The
readsettings ofObject FolderandDocument Folderare now applied in every position a folder can show up. A folder of a disabled type resolves tonull(or is left out of a list) inparent,childrenand_siblings, relations, relation editables of documents and element properties. Before, relations and the document tree returned the folder anyway, and unions of element properties could fail with a schema error for such a folder. Endpoints that rely on folders being returned from these positions have to enable thereadsetting of theObject Folder/Document Foldertype. See Folder Read Settings. - Thumbnails of image editables with a user selected crop are now cropped. For a
document_editableImagewhose crop area was set in the editor, the thumbnail fields (fullpath,data,srcset,dimensionsandresolutionswith athumbnailargument) apply that area, the way the frontend does. Without athumbnailargumentfullpathstill returns the original image. Clients that already read thecropfield and crop the thumbnail themselves must stop doing so, otherwise the crop is applied twice. Theresolutionsof asrcsetentry now follow the requestedformatargument like thesrcseturls do (before they were always in the original format).
GraphQL: a denying PermissionEvents::PRE_CHECK listener is now honoured with the default not allowed policy
WorkspaceHelper::checkPermission() ignored $event->setIsGranted(false) of a PermissionEvents::PRE_CHECK listener
unless the not allowed policy was NOT_ALLOWED_POLICY_EXCEPTION. With the default NOT_ALLOWED_POLICY_NULL the denial
is now applied too: the element is treated like one denied by the workspaces (omitted from lists, success: false for
mutations, null from getAsset/getDocument, an error from getObject; a denied image of an image editable in a
document create or update is cleared without failing the mutation). Projects that register a denying listener and
relied on the denial being ignored see elements disappear. A listener still cannot grant access that the workspaces
deny.
Upgrade to 2026.3.4
GraphQL
- The
updateAssetmutation now follows the workspace of the configuration, likeupdateObjectandupdateAssetFolder: theupdateright is required on the asset, and moving it to a newparentIdadditionally requires thecreateright on the new parent. Without the right the mutation answers withsuccess: false(or throws with the exception policy enabled). Configurations whose asset workspace entries are narrower than the assets they update throughupdateAssetneed wider entries if that access is intended. - The mutations that move or create elements apply the workspace to the target parent as well:
updateAssetFolder,updateObjectFolderandupdateDocumentFolderonly act on folders and require thecreateright on a newparentId;deleteAssetFolder,deleteObjectFolderanddeleteDocumentFolderonly delete folders and no longer delete other elements;updateObjectchecks theupdateright on the object where it is and now requires thecreateright on a newparentIdinstead of theupdateright (a move into a folder withcreatebut noupdateis accepted, a move of an object withoutupdatewhere it is now is refused), before changing anything;createAssetrequires thecreateright on aparentIdgiven insideinputtoo. Requests that relied on moving or creating elements outside the workspace now answer withsuccess: false. - The
filterargument ofgetAssetListingand the data object listing queries only accepts the documented JSON syntax: an object, or an array of objects, at every level (including inside$and/$orand field arrays). Any other value, such as a plain JSON string, is rejected with the errorinvalid filter: conditions must be JSON objectsinstead of being added to the listing condition. Filters written in the documented syntax are not affected. See Filtering. - The children of a
Blockfield insideLocalized Fieldsthat resolve their own value (for exampleDateand relation fields) are now read in the language requested with thelanguageargument of the block field, like the other children. Before, they came from the current locale instead of the requested language, so one block row could mix languages. Queries that request a language for such a block now return the values for that language, includinggetFallbackLanguageValuelike the other children.
Upgrade to 2026.3.0
GraphQL
- Added GraphQL query support for the
Renderletdocument editable. Document queries now expose renderlet editables through the newdocument_editableRenderlettype with the fields_editableType,_editableName,id,type,subtypeandrelation(the referenced element, resolved as ananytarget). This is a purely additive schema change; existing queries are not affected. Note that thetypefield returns the element type of the referenced target (asset,documentorobject), and unpublished targets resolve tonull(consistent with theRelationeditable).
Upgrade to 2026.2.8
Frontend Build Ships as a Packaged Archive
The compiled Studio frontend is no longer committed as an expanded
src/Resources/public/studio/build/ directory. It now ships as a single archive
(build-dist/build-<id>.zip) that is extracted into
src/Resources/public/studio/build/ automatically during cache warmup.
The already-required pimcore/studio-ui-bundle ^2026.2.5 provides the archive
extraction, so no dependency change is needed.
Note: Read-only filesystem deployments must run
bin/console cache:warmup(orcache:clear) during the build/deploy phase while the bundle directory (usually undervendor/) is still writable. Standard Pimcore deployments already do this. Whenassets:installruns in copy mode, runcache:warmupbefore it, otherwise no frontend assets are copied. If the filesystem becomes read-only before the first warmup, the bundle fails withBuildArchiveNotWritableExceptionbecause there is no build to serve.
Upgrade to 2026.2.6
GraphQL: unit of QuantityValue / InputQuantityValue is now null when no unit is set
Quantity value fields without a selected unit previously returned the unit field as an object whose
subfields were all null (e.g. "unit": {"id": null}). It is now null as the (nullable) schema
definition implies:
{ "length": { "value": 8500, "unit": null } }
Clients that access unit subfields unconditionally (e.g. data.length.unit.id) have to null-check
unit first.
Upgrade to 2026.1.0
PHP & Symfony Version Requirements
- Added support for
PHP8.5. - Removed support for
PHP8.3and Symfonyv6. - Minimum required Symfony version is now
^7.2(dev:^7.4forsymfony/runtime).
Removed ExtJS / Admin Classic UI
- Removed all ExtJS-based frontend JavaScript files (
src/Resources/public/js/), including the full configuration UI, field dialog, adapters, workspace editors, query and mutation operators. - Removed
ConfigController(previously provided the classic admin config API at/pimcore-datahub-webservices/explorer/{clientname}and related actions). - Removed
GraphQLExplorerController(previously served the ExtJS-based GraphQL Explorer at/pimcore-datahub-webservices/explorer/{clientname}). - Removed
AdminListener(no longer needed without classic admin integration). - Removed
StudioRouteLoader: Studio routes are now registered directly viarouting.ymlusing attribute-based routing. - Removed
ExportServiceandImportService(classic admin import/export, not related to Studio). PimcoreDataHubBundleno longer implementsPimcoreBundleAdminClassicInterfaceorDependentBundleInterfaceand no longer usesBundleAdminClassicTrait.- Removed dependency on
pimcore/admin-ui-classic-bundleandpimcore/compatibility-bridge-v10fromcomposer.json.
Routing Changes
- The Studio routing entry has been renamed from
pimcore_statistics_explorer_studiotopimcore_data_hub_studio. Update any references in custom routing configurations accordingly. - The separate
studio_routing.yamlfile has been removed; Studio routes are now defined directly inrouting.yml.
Studio Integration
- Added full Studio UI integration for GraphQL configurations (browse, create, edit, clone, delete, import, export).
- New Studio REST API endpoints added under
/pimcore-studio/api/bundle/data-hub/config/...(collection, add, get, update, clone, delete, import, export). - New Studio REST API endpoints added: GraphQL Explorer URL (
/pimcore-studio/api/bundle/data-hub/graphql/explorer-url/{name}), thumbnails, and user permissions. - New interfaces introduced for Studio services:
ConfigurationServiceInterface(src/Service/Studio/ConfigurationServiceInterface.php)ConfigurationHydratorInterface(src/Hydrator/ConfigurationHydratorInterface.php)ConfigurationDehydratorInterface(src/Hydrator/ConfigurationDehydratorInterface.php)ConfigurationDetailHydratorInterface(src/Hydrator/ConfigurationDetailHydratorInterface.php)GraphQLExplorerServiceInterface(src/Service/Studio/GraphQLExplorerServiceInterface.php)ThumbnailHydratorInterface(src/Hydrator/ThumbnailHydratorInterface.php)ThumbnailServiceInterface(src/Service/Studio/ThumbnailServiceInterface.php)PermissionUserHydratorInterface(src/Hydrator/PermissionUserHydratorInterface.php)UserServiceInterface(src/Service/Studio/UserServiceInterface.php)
- New pre-response events dispatched before Studio API responses:
ConfigurationEvent,ConfigurationDetailEvent,PermissionUserEvent,ThumbnailEvent
New GraphQL Events
- Added
ListingEvents::PRE_BUILDevent dispatched before building GraphQL query listings. Implement a listener on this event to modify listing arguments before the query is executed.
Return Type and PHPDoc Changes
PimcoreDataHubBundle::getInstaller()return type changed from?InstallerInterfacetoInstallerInterface(non-nullable).ElementPropertyType::resolveType()return type changed fromObjectType|string|callable|Deferred|nulltoObjectType|callable|null:stringandDeferredremoved from union.HotspotMetadataType::resolveType()return type changed fromObjectType|string|callable|Deferred|nulltoObjectType|callable|null:stringandDeferredremoved from union.DocumentType::resolveType()return type changed fromcallable|Deferred|ObjectType|null|stringtocallable|ObjectType|null.AbstractOperator::$childrenproperty PHPDoc type changed fromConfigElementInterface[]toarray:ConfigElementInterfacefromPimcore\DataObject\GridColumnConfigis no longer referenced.AbstractOperator::getChildren()return PHPDoc changed fromConfigElementInterface[]toarray.Service::buildOperator()parameter PHPDoc changed fromConfigElementInterfacetoarray.ReverseManyToManyObjects::resolve()return PHPDoc changed fromarray|nulltoarray.ElementMetadataKeyValuePairInputType::getInstance()return PHPDoc changed fromElementMetadataKeyValuePairInputType|nulltoElementMetadataKeyValuePairInputType.ClassificationstoreFeatureQueryTypeGenerator\Date::getFieldType()return PHPDoc changed fromDateType|nulltoDateType.Thumbnail::getLabeledValue()andThumbnailHtml::getLabeledValue()return PHPDoc changed from\stdClass|nullto\stdClass.DateFormatter::format()return PHPDoc changed fromCarbon|int|stringtoint|string.Link::resolveValue(),Link::resolveHref(),Link::resolveTarget(),Link::resolveLinkValue()return PHPDoc changed fromstring|null/nulltomixed.
Dependency Updates
- Removed Doctrine
enumtype mapping. The customenum: stringmapping is no longer required in Doctrine configuration.
2026.2.0
- [MutationType] Added system field
publishedas an optional argument for data object mutation
2.2.0
- [MutationType] Added system field
keyas an optional argument for data object mutation
2.0.0
- [General] Marked several classes as internal and/or final.
- [General] Added timezone indication for date and datetime fields in the GraphQL schema, including creation and modification date.
Therefore, the type of both date fields in the GraphQL schema have changed from
int(timestamp) tostring. - [Operator] Removed merge operator
- [Command] Removed RebuildDefinitionsCommand (
datahub:graphql:rebuild-definitions), use RebuildWorkspacesCommand (datahub:configuration:rebuild-workspaces) instead. - [Config] Removed DatahubConfigLocator class
- [Config] Removed support for legacy config file (
datahub-configurations.php) - [Config] Removed
getConfigModificationDatefrom config dao. - [Config] Removed sql query config field
- [QueryType]
args['path']will no longer be supported, useargs['fullpath']instead. - [DataType] Generated type names now include the type itself, see https://github.com/pimcore/data-hub/issues/879
- [QueryType] Change type name for
tabledefinition, now the name also includes the type, see https://github.com/pimcore/data-hub/pull/883 - [DataType] Added numeric-prefix
colfortablecolumns to allow numbers as column names
1.8.0
- [General] Dropped support of
pimcore/pimcorev10. Bumped minimum requirement ofpimcore/pimcoreto^11.2 - [General] Replaced Request::get() with explicit input sources.
- [Schema Definition] Added a button to add all definitions except system columns, along with multi drag-and-drop functionality using CTRL+ click to select and drag multiple fields to the configuration.
- [Schema Definition] A category selector with CTRL + click functionality was added, and the issue with deleting the entire configuration has been resolved.
1.7.0
- [GraphQL] Deprecated SQL Condition.
- [GraphQL] Added the possibility to disable deprecated SQL Condition.
1.6.0
- [General] If you want to use Datahub 1.6 and Pimcore 11, please make sure to require the
pimcore/admin-ui-classic-bundle. - [Config Location] Change default directory for configurations to
var/config/data_hub - When using Pimcore 11, configurations from
datahub-configurations.phpare no longer used. To migrate those configurations to the settings store, use the provideddatahub:configuration:migrate-legacy-configcommand. - Added the ability to import and export each type of Datahub configuration.
Be sure to include the
supported_typesconfiguration in any custom implementation to use the import functionality! - Added possibility to disable the introspection for GraphQL via configuration tree.
1.5.0
- When "Skip Permission Check" is active in a GraphQL configuration, the "Workspaces" settings are also skipped
- It is possible to add more than one API key per configuration now. Therefore, the API keys get stored as an array in the configuration. Configurations from previous versions are still supported, but they get converted to the new format as soon as they get saved.
- Added "Translation Listing" and "Translation" to the Generic Types