Affected Version
2026.2
Affected capability
Documents
Steps to reproduce
Create documents in Pimcore v12 containing an Areablock with multiple content items.
Add editable fields inside those Areablock items, such as text fields, images, relations, checkboxes, or configuration values.
Upgrade the existing project and database from Pimcore v12 to Pimcore v2026.2.
Open one of the existing documents in the Pimcore editor.
Save the document without adding, removing, or reordering any content.
Reopen the document.
Actual Behavior
The existing document content was originally created in Pimcore v12.
Each item inside the Areablock has an identifier, and the editable fields belonging to that item include the same identifier in their names.
For example, an existing Areablock item and its fields may have been stored in Pimcore v12 as:
content:12
content:12.title
content:12.image
content:12.settings
After upgrading to Pimcore v2026.2, the document initially opens and displays the existing data correctly.
However, when the document is saved, Pimcore v2026.2 creates the parent Areablock structure using different sequential identifiers. For example, the same item may now be stored as:
content:9
During the same save operation, the request still sends the nested editable fields using their previous Pimcore v12 identifiers:
content:12.title
content:12.image
content:12.settings
The saved parent item therefore uses content:9, while its editable fields still use content:12.*.
This causes the parent item and its editable fields to become disconnected.
When the document is opened again, Pimcore searches for editable fields under the new parent identifier:
content:9.*
but the existing values are still stored under:
content:12.*
As a result, the editable values no longer appear in the document editor.
This may affect any editable field placed inside an Areablock item, including text, images, relations, selections, and configuration fields.
The data may still exist in storage, but it is stored under the previous identifier and is no longer associated with the current Areablock item.
The issue occurs simply by opening and saving an existing document after the upgrade. No reordering, adding, or removing of Areablock items is required.
Expected Behavior
When an existing Pimcore v12 document is opened and saved in Pimcore v2026.2, the relationship between every Areablock item and its editable fields should be preserved.
If Pimcore changes the identifier of an existing Areablock item during the save operation, all editable fields belonging to that item should automatically be changed to use the same identifier.
For example, when the parent item changes from:
content:12
to:
content:9
its editable fields should also change from:
content:12.title
content:12.image
content:12.settings
to:
content:9.title
content:9.image
content:9.settings
Saving an existing document after upgrading from Pimcore v12 to Pimcore v2026.2 should not cause existing editable values to disappear or become disconnected from their Areablock items.
Affected Version
2026.2
Affected capability
Documents
Steps to reproduce
Create documents in Pimcore v12 containing an Areablock with multiple content items.
Add editable fields inside those Areablock items, such as text fields, images, relations, checkboxes, or configuration values.
Upgrade the existing project and database from Pimcore v12 to Pimcore v2026.2.
Open one of the existing documents in the Pimcore editor.
Save the document without adding, removing, or reordering any content.
Reopen the document.
Actual Behavior
The existing document content was originally created in Pimcore v12.
Each item inside the Areablock has an identifier, and the editable fields belonging to that item include the same identifier in their names.
For example, an existing Areablock item and its fields may have been stored in Pimcore v12 as:
content:12
content:12.title
content:12.image
content:12.settings
After upgrading to Pimcore v2026.2, the document initially opens and displays the existing data correctly.
However, when the document is saved, Pimcore v2026.2 creates the parent Areablock structure using different sequential identifiers. For example, the same item may now be stored as:
content:9
During the same save operation, the request still sends the nested editable fields using their previous Pimcore v12 identifiers:
content:12.title
content:12.image
content:12.settings
The saved parent item therefore uses content:9, while its editable fields still use content:12.*.
This causes the parent item and its editable fields to become disconnected.
When the document is opened again, Pimcore searches for editable fields under the new parent identifier:
content:9.*
but the existing values are still stored under:
content:12.*
As a result, the editable values no longer appear in the document editor.
This may affect any editable field placed inside an Areablock item, including text, images, relations, selections, and configuration fields.
The data may still exist in storage, but it is stored under the previous identifier and is no longer associated with the current Areablock item.
The issue occurs simply by opening and saving an existing document after the upgrade. No reordering, adding, or removing of Areablock items is required.
Expected Behavior
When an existing Pimcore v12 document is opened and saved in Pimcore v2026.2, the relationship between every Areablock item and its editable fields should be preserved.
If Pimcore changes the identifier of an existing Areablock item during the save operation, all editable fields belonging to that item should automatically be changed to use the same identifier.
For example, when the parent item changes from:
content:12
to:
content:9
its editable fields should also change from:
content:12.title
content:12.image
content:12.settings
to:
content:9.title
content:9.image
content:9.settings
Saving an existing document after upgrading from Pimcore v12 to Pimcore v2026.2 should not cause existing editable values to disappear or become disconnected from their Areablock items.