[PAGES-339] Not able to delete uploaded image Created: 07/Sep/20  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 6.2.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Monica Damborenea Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File image.yaml     PNG File test1.png    
Issue Links:
Relates
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:
Epic Link: UI framework implementation
Story Points: 5

 Description   

When uploading a file of type damUploadField it is not possible to delete it afterwards.

Steps to reproduce

  1. Create a new component definition, you can test it using the dialog attached image.yaml.
  2. Go to the pages app and create a component.
  3. Choose "upload", upload an image and save
  4. Open up the dialog again and delete the image 
  5. Open again the dialog: the image has not been removed, you can still see it in the dialog and in JCR.

Expected results

The image should be removed.

Dev notes

  • Let's check if this is a problem also with uploadField
  • damUploadField used by customer in support - do we need to anything about that? - in MGNLDAM-880 there's a breaking change for this
  • It seems work on "normal" upload field (in contact, asset app). But in here, damUploadField in component in page app.


 Comments   
Comment by Roman Kovařík [ 10/Mar/21 ]

Not able to reproduce on latest https://demo.magnolia-cms.com/.magnolia/admincentral#app:dam:jcrDetail;/travel-demo/social-icons/google-plus.png:edit

Generated at Mon Feb 12 06:17:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.