[MGNLDAM-985] Allow to modify path in damLinkField Created: 13/Apr/21 Updated: 14/Oct/21 Resolved: 03/Sep/21 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | 3.0.9 |
| Fix Version/s: | 3.0.10 |
| Type: | Improvement | Priority: | Blocker |
| Reporter: | Viet Nguyen | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 2 |
| Labels: | cs-bk, maintenance, ui-team-support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.2h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| 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
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||
| Epic Link: | Improve Content Linking | ||||||||||||||||||||||||||||||||
| Sprint: | UI FW 35, UI FW 36 | ||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||
| Description |
|
Steps:
Current:
Expected:
This work previously and now it does not in 6.2.7.
Developer notes:
|
| Comments |
| Comment by Roman Kovařík [ 13/Apr/21 ] |
|
Should be possible with textInputAllowed=true and showOptions=true. |
| Comment by Stefan Huettenrauch [ 13/Apr/21 ] |
|
Hi Roman, we've tried the options you named. Yes, we can edit the path field, BUT (tested on 6.2.6) Could you please check on your end. |
| Comment by Roman Kovařík [ 13/Apr/21 ] |
|
Hi shuettenrauch, The new showOptions property is available since MGNLUI-6530. Just tried to validate: Untitled 2.mov Hope that helps |
| Comment by Roman Kovařík [ 13/Apr/21 ] |
|
Hey Viet, |
| Comment by Stefan Huettenrauch [ 13/Apr/21 ] |
|
thanks for your fast answer. we will upgrade to 6.2.7 in the next week and then be back with our results. |
| Comment by Jonathan Ayala [ 16/Apr/21 ] |
|
This issue has also been reported in SUPPORT-12918. Steps to reproduceIt can be reproduced with mtk components in pages app:
Results:In 2) field is editable, i.e. Link field (to pages) is generated as editable. Although both components are defined almost equally, generation of LinkField in {info.magnolia.ui.form.field.definition.migration.LinkFieldDefinitionConverter<T>}} differs when target workspace is dam, which is probably what is causing the distinction. |
| Comment by Roman Kovařík [ 01/Oct/21 ] |
|
damLinkField with textInputAllowed=true now accepts path to an asset as direct input (has to be explicitly enabled). |