[RESPDAM-85] Focal point default information is stored invalid when uploading using multi upload Created: 08/May/23  Updated: 23/May/23  Resolved: 23/May/23

Status: Closed
Project: DAM Focal
Component/s: None
Affects Version/s: 2.4
Fix Version/s: 2.4.1

Type: Bug Priority: Medium
Reporter: Tobias Kerschbaum Assignee: Raphael Falvo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File Focal-Error.log     PNG File image-2023-05-08-10-59-49-008.png    
Issue Links:
Problem/Incident
is caused by RESPDAM-80 Focal areas/point default information... Closed
Relates
relates to RESPDAM-83 JCR default values for variations Closed
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
[X]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Team: Services
Work Started:

 Description   

Steps to reproduce

  1. Upload a new asset using upload with zip upload
  2. Use one of the uploaded images in a headless page (with the 
    AssetFocalReferenceResolver)

Expected results

The page should render and the image should be visible.

Actual results

Page is not rendering and the following error is thrown in the backend. (Focal-Error.log

Development notes

It seems that there are 2 properties that need to be included. The x and y value under:

  • property /Archive-2/Feature-1.png/focalPoint/x
  • property /Archive-2/Feature-1.png/focalPoint/y

See Screenshot. As soon as I add them (or open the image once and save it in the dam app) the Image can be rendered.

 



 Comments   
Comment by Raphael Falvo [ 08/May/23 ]

RESPDAM-80 change was wrongly writing focal point structure in JCR. Coordinates for focal points need to be written at asset level, as it is the same for all variations.

Comment by Raphael Falvo [ 23/May/23 ]

Will be released in version 2.4.1

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