-
Bug
-
Resolution: Duplicate
-
Neutral
-
None
-
1.1.3
-
None
Problem
When a template definition defines an area with no available components, then the "problems" sub app of the definition app will not start up, because of an NPE in TemplateDefinitionValidator line 97. areaDefinition.getAvailableComponents() returns null here, but it's not checked.
Especially a class like the TemplateDefinitionValidator should be very robust towards invalid or senseless template definitions.
Testcase
This template definition will crash the definitions app:
class: info.magnolia.module.site.templates.PageTemplateDefinition
renderType: site
type: feature
parameters:
allowedSubTemplates:
areas:
main:
type: list
availableComponents:
footer:
editable: false
Acceptance criteria
- duplicates
-
MAGNOLIA-7351 Setting a property to null via YAML configuration should report a problem
- Closed