Upgrade Information
The following steps are necessary during updating to newer versions.
Upgrade to 2026.3.5
- [Security] Alternative Element Trees: the Symfony expression of a relation tree level
(
relationSymfonyExpression) is now evaluated with read-only values of the related object (GHSA-x6vx-2g29-6ff4). Symfony's ExpressionLanguage is not a sandbox: anyone allowed to edit tree configurations could call every public method of the related object, e.g. reach the database connection throughobject.getDao(), or save or delete elements. Field getters (also of related objects, object bricks, field collections and localized fields, e.g.object.getName("de")), element getters (getId(),getKey(),getFullPath(),getParent(), dates, ...), the getters of field values and operators like~keep working, e.g.object.getName() ~ " " ~ object.getManufacturer().getName(). Any other method, e.g.getDao(),save(),delete(), setters,getClass()orgetChildren(), is rejected: saving such a tree configuration fails validation, and a stored one fails when the tree is built. Theconstant()function stays unavailable. See the Pimcore core upgrade notes on expressions for the full list. pimcore/pimcore^2026.3.5is now required, as it provides the read-only expression language.
Upgrade to 2026.3.4
- Alternative Element Trees: the hash that detects whether an object's tree rows must be rebuilt now keeps empty
levels and the borders between levels. Stored hashes change, so each object is re-checked the next time it is
saved and its rows are rebuilt once. To repair trees that already hold stale rows, run
bin/console bpt:aet:rebuild-tree -a.
Upgrade to 2026.3.3
- Duplicate detection: a sweep page whose search request times out (
cluster_courtesy.request_timeout_ms) or comes back with a failed shard now aborts that sweep step, so the run ends finished with errors instead of silently finished with incomplete results. The failed page is not checkpointed, so the run never records progress past what it missed. The run keeps a single resume cursor, though: once the fuzzy tier has checkpointed, a retry of a failed exact sweep starts from the beginning rather than at the last exact page. If runs now end with errors, raiserequest_timeout_msor check the search cluster's health. - Duplicate detection: a run that stopped at an execution budget before covering every element now shows a warning on the duplicates configuration screen.
Upgrade to 2026.3.2
- Duplicate detection: the path restriction of a scope or class is now a list of include/exclude folder
rules (
paths) and applies to group members as well as references, in both the exact and the fuzzy tier. Previously the fuzzy tier could group elements from outside the configured path. The next analysis withdraws such members; no full run is needed. path_prefixis deprecated; it is read as one include rule. Replace it withpaths, see Folder rules.- A path now covers whole folders only:
/Productsno longer matches/Products-Old. - Studio API: the duplicates configuration schemas carry
paths(list of{path, mode}); the formerpathPrefixis deprecated and, whenpathsis empty, still read as one include rule.
Upgrade to 2026.3.0
- Added Embeddings (experimental) – off by default.
- New public API -
EmbeddingProviderInterface,AbstractHttpEmbeddingProvider,EmbeddingModelConfigandEmbeddingConfigExceptionare public so a custom provider can be implemented.
Embeddings are adding a new table, please execute the migration command after updating the bundle:
bin/console doctrine:migrations:migrate --prefix='Pimcore\Bundle\BackendPowerToolsBundle\Migrations'
Upgrade to 2026.2.6
Frontend Build Ships as a Packaged Archive
The compiled Studio frontend is no longer committed as an expanded
public/studio/build/ directory. It now ships as a single archive
(build-dist/build-<id>.zip) that is extracted into public/studio/build/
automatically during cache warmup.
pimcore/studio-ui-bundle ^2026.2.1 is now required, as it provides the
archive extraction.
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.1.0
- The bundle installer now implements
PostInstallCommandsProviderInterfacefrom Pimcore's InstallBundle. This means the post-install commandbpt:aet:rebuild-tree -ais automatically executed duringpimcore:installwhen using Install Profiles. Manual execution of this command afterpimcore:bundle:installis still required as before. - The messenger transport DSN is now configurable via the
%pimcore.messenger.transport_dsn_prefix%container parameter instead of being hardcoded todoctrine://default. This allows the installer to wire the transport DSN from environment variables (e.g.PIMCORE_MESSENGER_TRANSPORT_DSN_PREFIX). - Added support to
PHP8.5. - Removed support to
PHP8.3and Symfonyv6.