[MAGNOLIA-7636] "Bean Property is Skipped" Error Created: 24/Sep/19  Updated: 14/Oct/21  Resolved: 11/Oct/19

Status: Closed
Project: Magnolia
Component/s: node2bean
Affects Version/s: 6.1, 6.1.1, 6.1.2
Fix Version/s: 6.1.3, 6.2

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File debug_screenshot.png     PNG File problemsTab.PNG    
Issue Links:
causality
caused by MAGNOLIA-6521 Module config via Light Module Closed
relation
is related to MAGNOLIA-6521 Module config via Light Module Closed
is related to MAGNOLIA-7549 Arrays in beans in module configurat... Accepted
is related to MAGNOLIA-4685 n2b: resolve support for 'enabled' flag Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Support
Sprint: UI Framework 8
Story Points: 3

 Description   

Area nodes from site prototypes are returning null. As a result, areas cannot be rendered from prototypes. They can be read and show up while debugging, but as empty nodes. Definitions app shows a "Bean property is skipped" error. See screenshot for more details.

This seems to be related:
https://jira.magnolia-cms.com/browse/MAGNOLIA-7549

Possible side effect of completing:
https://jira.magnolia-cms.com/browse/MAGNOLIA-6521



 Comments   
Comment by Federico Grilli [ 22/Oct/19 ]

mdrapela/docuteam 
I guess it's worth mentioning somewhere in our documentation that a bean in Magnolia configuration can have three states represented by the Boolean property enabled

  • enabled = true (default in most cases, no need to specify it)
  • disabled = false
  • inherited/undefined = null

 the latter allows for a configuration bean to be merged with its parent, e.g. an area from a page template definition can get its values from a prototype.

Generated at Mon Feb 12 04:25:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.