[MGNLUI-6991] Cannot Delete An Asset From a DAM Upload Field Created: 15/Dec/21  Updated: 16/Feb/22  Resolved: 24/Jan/22

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.9
Fix Version/s: 6.2.16

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: VN-Testing, cs-bk
Remaining Estimate: Not Specified
Time Spent: 5h
Original Estimate: Not Specified

Attachments: HTML File field_example    
Issue Links:
Problem/Incident
Relates
relates to MGNLUI-7017 Model content with file/binary proper... Accepted
relation
is related to MGNLPN-611 Migrate personas photo to dam Open
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)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Release notes required:
Yes
Date of First Response:
Sprint: Nucleus 2
Story Points: 3

 Description   

Steps To Reproduce

  • Add an upload field for assets to a dialog (can be a content app dialog or a page dialog - I've attached a sample field)
  • Open this dialog
  • Upload an asset to this field
  • Save the Dialog
  • Reopen the dialog
  • Click on the delete button the field (the small garbage can icon)
  • Save the dialog
  • Reopen the dialog yet again

Expected Result
The upload field is blank, the old image was successfully removed.

Actual Result
You will see that the image was never deleted, it is still there in the field.

Additional Notes
The image will be removed successfully if you do not save the dialog.
Happens on page dialogs and content app dialogs.



 Comments   
Comment by Adam Siska [ 24/Jan/22 ]

RN for both MGNLUI-6990 and MGNLUI-6991:
DamUploadView works also without required flag and once uploaded and saved file could be removed from existing asset.

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