Currently we are working on a PIM project (Pimcore 6.3.6) that uses localized fields heavily. Underneath a simplified example of how our Product Class definition looks like.
product
general
localizedfields
name
attributes
ObjectbrickTypeA
localizefields
supplierName
MultiSelectTags
We followed the mapping using xdebug and came across a bug when using the localizefield in a Objectbrick.
For the localized fields the mapping is done by the "MapStructuredValue" class. And the objectBricks are mapped by "MapObjectBricks" class.
Our products are mapped according the structure MapObjectBricks which goes into MapStructuredValue for ObjectbrickTypeA. In the structured value a ClassDefinition is selected to retrieve it's fields. When the mapper is inside the ObjectbrickTypeA the class name parent class 'Product' is used instead of the objectbrick name. Because of this the mapper is unable to get the fields for the object brick and throws an error getFieldDefinitions() on null.
Currently we are working on a PIM project (Pimcore 6.3.6) that uses localized fields heavily. Underneath a simplified example of how our Product Class definition looks like.
product
We followed the mapping using xdebug and came across a bug when using the localizefield in a Objectbrick.
For the localized fields the mapping is done by the "MapStructuredValue" class. And the objectBricks are mapped by "MapObjectBricks" class.
Our products are mapped according the structure
MapObjectBricks
which goes intoMapStructuredValue
forObjectbrickTypeA
. In the structured value a ClassDefinition is selected to retrieve it's fields. When the mapper is inside theObjectbrickTypeA
the class name parent class 'Product' is used instead of the objectbrick name. Because of this the mapper is unable to get the fields for the object brick and throws an errorgetFieldDefinitions() on null
.