[MAGNOLIA-1537] AdminTreeMVCHandler could accept tree path property for dynamic tree configuration Created: 18/May/07  Updated: 23/Jan/13  Resolved: 13/Jan/09

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: None
Fix Version/s: 4.0

Type: Improvement Priority: Major
Reporter: zam6ak Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1538 Tree does not work if setPath() is us... Closed
is related to MGNLDMS-99 Creating custom tree configuration fo... 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)
Date of First Response:

 Description   

Currently there is no way to specify a start path for a an existing tree.
Path has to be set up in custom tree configuration java file which makes trees less reusable.

For example, if I needed a website tree in a dialog link controll that starts from /site1/folder1/ I would have to make new custom tree configuration that extends website tree and sets the path.
Instead, it would be nice if I could just make a copy of the website tree configuration node and specify path = /site1/folder1.



 Comments   
Comment by Magnolia International [ 10/Sep/08 ]

Indeed, there is currently no other way than having a custom TreeConfiguration to achieve this - see linked issues. When trees will be instanciated and configured using content2bean, this should be rather trivial to implement without the need for a custom TreeConfiguration for each and every path.

Comment by Philipp Bracher [ 13/Jan/09 ]

One can now set a rootPath property in the tree configuration

Generated at Mon Feb 12 03:27:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.