-
Bug
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
Features 6
-
3
Thanks to mchruscielewski in SUPPORT-8899, "availableComponents" field but has no subfields in yaml area definition caused NPE.
Sample config:
templateScript: /website/templates/components/pages/globalcoverage/country_overview.ftl renderType: freemarker title: Global coverage - country overview areas: countries: type: list renderType: freemarker availableComponents:
First round investigation from customer:
info.magnolia.rendering.template.registry.validator.TemplateDefinitionValidator protected void validateArea(DefinitionProvider<TemplateDefinition> definitionProvider, Collection<Problem> problems, String rootPath, AreaDefinition areaDefinition) { areaDefinition.getAvailableComponents().forEach((componentName, componentAvailability) -> { ... }
caused NPE.
- is causing
-
MGNLTPLSMPL-34 yaml definitions contains properties with null value
- Closed
-
MAGNOLIA-7482 DOC: Setting empty value in list and map YAML properties
- Closed
- is duplicated by
-
CFGUI-77 NPE when area as no availableComponents
- Closed
-
CFGUI-79 problems handling broken definitions gracefully - availableComponents
- Closed
- is related to
-
MAGNOLIA-8903 Problems handling broken definitions gracefully - areas
- Closed
-
CFGUI-114 Add DEBUG to #validateDefinition() in case of exceptions
- Closed
- relates to
-
MGNLUI-5260 multi-reference properties are broken - storing paths instead of UUID
- Closed