-
Bug
-
Resolution: Fixed
-
Critical
-
4.2.0
-
None
-
None
-
4.2 RC2
Example :
- We have 2 content types A and B
- B extends A
- A defines an attribute of type content.
- In this attribute, the referenced content type is B
Here is the parsing behavior:
- A is parsed before B
- The content attribute defined in A is parsed
- We check that the refernced content type (B) exists => KO. It does not exist because it will be parsed after A.
Solution:
Like before the CMS-9613, check the attributes of type content in ContentType.postInitialize() method