- 🇨🇦Canada mlizarraga
I have the same issue, I wonder if would be better if instead of storing the values for the fields, this should be storing the serialized value this way we avoid the error but there should be a bit more work from the import section.
I'm assuming without any further investigation that we could just deserialize it when we assign the value for the same field, I think that should work.
The current problem is that trying to store the object (class) for the Layout Section cause this error if we serialize the value the error is gone, obviously we will have an issue with the import.