[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: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| 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: Possible side effect of completing: |
| Comments |
| Comment by Federico Grilli [ 22/Oct/19 ] |
|
mdrapela/docuteam
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. |