[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: |
|
||||||||||||
| 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. 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. |
| 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 |