[MGNLUI-6644] Default JCR Chooser shows system nodes Created: 01/Apr/21 Updated: 05/May/21 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | dialogs |
| Affects Version/s: | 6.2.6, 6.2.7 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Chris Jennings | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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: |
| Description |
Steps to reproduce
Expected results
Actual results
Workaround# I think the default app could be extended to explicitly filter nodes by type. Development notes |
| Comments |
| Comment by Chris Jennings [ 01/Apr/21 ] |
|
It is possible to configure a minimal datasource and chooser dialog. thing-chooser.yaml class: info.magnolia.ui.chooser.definition.SingleItemWorkbenchChooserDefinition workbenchChooser: datasource: $type: jcrDatasource workspace: <YOUR-WORKSPACE> allowedNodeTypes: - <YOUR-TYPE> - <ANOTHER-TYPE> Then extend the app YAML file like: things.yaml subApps: detail: form: properties: <LINKED-PROPERTY-NAME>: chooserId: YOUR-MODULE:thing-chooser |
| Comment by Roman Kovařík [ 05/May/21 ] |
|
For the record, the datasource could be defined at link field level, there should be no need to configure a custom chooser, e.g.:
$type: linkField
datasource:
$type: jcrDatasource
workspace: dam
allowedNodeTypes:
- mgnl:asset
- mgnl:folder
|