Details
-
Bug
-
Resolution: Cannot Reproduce
-
Neutral
-
None
-
6.2.3
-
None
-
-
Empty show more show less
-
DevX 34
-
5
-
Yes
Description
When having a template prototype whose configuration values are override in another page definition, these are not correctly merged from the prototype to the template and as a consequence, prototype values must be set again in the page definition.
Test scenario:
We have the following prototype definition in which test-area and subarea set their templateScript properties as well as disable them by default:
In certain page template we want to enable them so that we define enabled property to true:
test-area:
enabled: true
areas:
subarea:
enabled: true
Expected result:
Both areas are enabled and the corresponding templateScript is rendered
Actual result:
templateScript is not populated from the prototype to the page template while merging and resulting rendition is not the expected one.
Dev Notes:
Adding the templateScript property to the page template again is necessary to get the expected result.
test-area:
enabled: true
templateScript: /mtk/templates/pages/test-area.ftl
areas:
subarea:
enabled: true
templateScript: /mtk/templates/pages/subarea.ftl
This has been tested in 5.7.8 successfully, values are populated and corresponding scripts rendered.