[MGNLUI-6199] "targetTreeRootPath" Property Is Affecting Pages App Hierarchy When Included On A Magnolia 5UI Dialog Containing A Link Field Created: 08/Sep/20  Updated: 22/Sep/21  Resolved: 08/Jan/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.2
Fix Version/s: 6.2.6

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Thuy To
Resolution: Fixed Votes: 2
Labels: 623, cs-bk, maintenance
Remaining Estimate: Not Specified
Time Spent: 7d 7.7h
Original Estimate: Not Specified

Attachments: File treeRootPathTest_component.ftl     File treeRootPathTest_component.yaml     File treeRootPathTest_component_dialog.yaml    
Issue Links:
causality
relation
is related to MGNLUI-6004 LinkFieldDefinitionConverter doesn't ... 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
Date of First Response:
Epic Link: UI framework: migration and backwards compatibility
Sprint: Maintenance 37, Maintenance 38, Maintenance 39
Story Points: 2

 Description   

If you configure a component o have a link field containing the property : “targetTreeRootPath” and setting it to any parent node in the pages app hierarchy, then the pages that get displayed on the pages app become the child nodes of this root path.

I have attached the files I was working with. You can use them to test as well.

Steps:

  • Create a component with a link field that contains the property “targetTreeRootPath” (Or use the component "treeRootPathTest_component")
  • Create a page and add this component to the page.
  • Open the page and open the dialog for the component
  • At this point, no edits have to be made on the dialog, simply opening the dialog is enough
  • Close the dialog.
  • Close the page.
  • Access the pages app again

Actual Result
You will see that the pages displayed are now those under the dialog's configured “targetTreeRootPath”

Expected:
TargetTreeRootPath should only affect dialog link field choosing windows. It should not affect anything else.

 This is happening with the Magnolia 5 UI Framework within Magnolia 6.2.2

Also check 6.2.3 to make sure. It's likely the old configuration converted into new framework?



 Comments   
Comment by Roman Kovařík [ 26/Nov/20 ]

Fix of the definition:
form:
  tabs:

  • name: tabMain
      fields:
  • name: something
    class: info.magnolia.ui.form.field.definition.LinkFieldDefinition
    targetTreeRootPath: /testing_root
    appName: pages-app pages

Targeting the new pages app in the old dialog doesn't make sense (such dialog wouldn't work in the old apps anyway).
You can either target the old pages app (pages) or just write the new framework config.

Generated at Mon Feb 12 09:34:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.