[PAGES-571] Passing content attribute from parent noComponent to child noComponent ends in invalid action bar Created: 07/Mar/22  Updated: 16/Aug/22  Resolved: 08/Jul/22

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.2.16
Fix Version/s: 6.2.20

Type: Bug Priority: Neutral
Reporter: Carlos Cantalapiedra Assignee: Lam Nguyen Bao
Resolution: Fixed Votes: 0
Labels: VN-Analysis
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 3d 3.5h Time Spent: 3d 3.5h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: Zip Archive my-company.zip    
Issue Links:
Problem/Incident
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-681 QA Sub-task Closed Andrei Ichimescu  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: AuthorX Support
Sprint: AuthX 13
Story Points: 5
Team: AuthorX

 Description   

Steps to reproduce

  1. Edit a page yaml to have a main area (called mainArea for this example) with type noComponent and a child area (called htmlHeader) with type noComponent
  2. On the page FTL, set the content attribute as follows: 
    basic.ftl
    [@cms.area name="mainArea" content=content/]
  3. Now at mainArea FTL, pass the content attribute to the child area (htmlArea):
    mainArea.ftl
     [@cms.area name="htmlHeader" content=content/]
  4. Finally, on the htmlHeader file, consume the content:
    htmlHeader.ftl
    <div>
        This is an htmlHeader area - cannot add components but we can consume some field from dialog
        <br/>
        field value : ${content.htmlHeaderTitle}
    </div>
  5. Check that the value is properly printed but if you clic on the area, no actions are shown on the action bar.

Expected results

Actions are shown on the action bar

Actual results

Only Edit page properties and Preview page actions are available

Workaround

N/A

Development notes

Investigation lead us to confirm that it happens because area action bar is only available when a mgnl:area node takes part. Therefore, when passing the content attribute of a noComponent type area, which doesn't have the corresponding mgnl:area node, this section is not visible. 

It wasn't happening on Magnolia 5.X


Generated at Mon Feb 12 06:20:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.