Pimcore 11: What the Platform Upgrade Changes for PIM Teams

Pimcore 11 is a platform upgrade. If you run Pimcore as your PIM, budget engineering time. The product team feels three changes: range attributes on data objects, custom document and asset types, and PDF previews through Gotenberg. The other work, 840 resolved issues and pull requests, is there so the core stays maintainable.

Pimcore published the release on 17 May 2023. The note by Bastian Zechmeister, content marketing manager at Pimcore, is the source for what follows, and it applies to both the Community Edition and the Enterprise Edition. The release note is written for developers. Read it that way.

The core gets stricter so later changes hurt less

Less-used features moved into bundles, which leaves a smaller core. Native PHP types now sit on parameters and return values, so a type error shows up before production. Test coverage and static analysis were extended across packages. Webpack packs the JavaScript and CSS of the admin UI, which is a maintenance choice for that UI, not a redesign of the screens a merchandiser lives in. Content Security Policy is on by default for the admin interface, aimed at cross-site scripting and injection. That is a security default your marketing team will not notice, and your engineers should not turn off to make an old plugin happy.

PHP 8.1 is the floor, Symfony is 6.2

Pimcore 11 runs on PHP 8.2 and requires PHP 8.1 as the minimum. Symfony, one of the large dependencies, moved to 6.2. Third-party dependencies were brought to current versions. Pimcore says the PHP line brings security fixes for at least three years and the Symfony line patches for at least four. That is their reading of upstream support, not a warranty you can put in a contract. The practical consequence is simpler: if you are still on an older PHP, the upgrade starts with the runtime, not with a workshop about attributes.

Technical debt comes out, including code you may have hooked

Deprecated features, old compatibility layers and custom implementations of things Symfony now provides (session handling and authentication among them) were removed. That is how a core stays explainable. It is also how a quiet customization breaks on the weekend of the upgrade. Diff your overrides against the upgrade notes before you pick a date. The PIM implementation guide treats that kind of upgrade as a project with an owner, which is the right shape here. A "we will click update on Friday" plan is how you discover the override.

Three changes a product modeler can point at

An abstraction layer now sits in front of the WYSIWYG editor, with TinyMCE as the default, so another editor can be attached through an extension. Gotenberg generates previews of Word, Excel and PowerPoint assets and PDFs in the web-to-print module, and it runs as a microservice (a Docker container is the example Pimcore gives). Someone has to operate that container. Custom document and asset types can be added through extensions, including a route to 3D files. Data objects gained range types: number range, quantity value range and date range.

Those range types and custom assets are the part that belongs in a feature conversation. PIM features and what they cover is the list to set them against: a temperature range or a pack-size range is a modeling win, and it does not replace workflow, rights or channel publishing. Gotenberg matters if you still make PDFs from the PIM. If you do not, it is infrastructure you can schedule later.

Extensions have to come along

Pimcore updated its extensions so they work with version 11, and brought extension labels into the same POEditor translation flow as the core. If you depend on a partner extension or one your own team wrote, compatibility is a line in the upgrade plan, not a hope. A platform with a strict core and a broken extension is a PIM you cannot open on Monday.

If you are still choosing whether Pimcore is the PIM, do not score this release by its adjectives. Score the data model, who maintains the extensions, and whether your team can carry a PHP and Symfony upgrade. How to select a PIM is that test. The trade-off on 11, for teams already live, is calendar versus drift: do the upgrade while the notes are current, and accept a few weeks of engineering, or postpone it and meet the same break later with less memory of why the override existed.