-
Bug
-
Resolution: Fixed
-
Major
-
4.1.0
-
None
-
None
-
4.2 M5
How to reproduce:
- Create a content type that extends 2 content types
- The 2 parents have a view with the same name that is not overriden by the child.
- The child has a merge of the views from its parents => OK
- But the merged view has a wrong order. The order of items in the merged view should reflect the order of the extends declaration in child content type but it doesn't => KO
The issue here is that the super-type array is sorted in a method to get merged view in cache. So the declaration order is not kept.
How to resolve : to find the merged view in cache, use a clone of the super-types array.
- Référence
-
CMS-9284 Parse the content type's views with the new API
- Closed