[AMPLIENCE-1] It's possible to generate 404 errors by selecting non-images Created: 17/Nov/21  Updated: 01/Dec/21  Resolved: 01/Dec/21

Status: Resolved
Project: Amplience DAM Connector
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Brandon Murdoch Assignee: Raphael Falvo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2021-11-17 at 13.41.37.png     Text File ampl-bug.log    
Template:
Acceptance criteria:
Empty
Date of First Response:
Story Points: 16

 Description   

Steps to reproduce

  1. Open a component dialog with a amplience field
  2. Navigate down the tree to an item in amplience that is not an image, for example a PDF
  3. select it, and an error will be generated in the magnolia UI behind the dialog.
  4. It's still possible to save this item - but will most likely not work in rendering

Log that is generated: 

ampl-bug.log

Expected results

No error from selecting these nodes should be raised.

Perhaps a validator could be added so that non-images can't be saved too?

Actual results

Error raised in the background UI

Workaround

 

Development notes



 Comments   
Comment by Brandon Murdoch [ 17/Nov/21 ]

If you save a none image in the dialog (including a folder) and then reopen the dialog, you will get a 500 error too / and the component dialog will not actually open. 

 

Comment by Raphael Falvo [ 23/Nov/21 ]

Hello bmurdoch, I'm unable to reproduce this issue on my side, using a very simple dialog with the amplienceLinkField.

May you please share here the dialog definition with which you are encountering the problem ? Thank you

Comment by Joe Fallon [ 30/Nov/21 ]

This still happens. I think this is caused by the preview lookup, it's trying to display the selected "image" but as it's not an image it can't display. 

Comment by Raphael Falvo [ 01/Dec/21 ]

This is fixed in up coming release

Generated at Sun Feb 11 23:11:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.