[RESPDAM-84] focalAreas will not be updated after uploading a new media in an existing asset Created: 19/Apr/23  Updated: 09/Jun/23  Resolved: 09/Jun/23

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

Type: Bug Priority: Critical
Reporter: Marc Johnen Assignee: Raphael Falvo
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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:
Team: Services

 Description   

Steps to reproduce

  1.  Upload an image in the assets app. A focalAreas node will be created with data for the different variations.
  2.  Open the image created before and upload another media. The focalAreas node will not be updated.

In /dam-focal-area/decorations/observation/config.yaml an event is configured to only trigger FocalAreaAssetObservation when a node is added, this is not enough.

Expected results

When uploading a new media in an old asset, focalAreas should be updated.

Actual results

When uploading a new media in an old asset, focalAreas stay the same. When the client uploads a new media this results in the image being cropped in a wrong way.

Workaround

Development notes



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

Hello marc.johnen 
Can you please specify which version of dam-focal module you are using ?
I tried to reproduce the issue, but I cannot. When uploading another image, the focal areas are correctly reset to default values in the center of the image.

Comment by Raphael Falvo [ 09/Jun/23 ]

Hi,

This issue has been inactive and "waiting for customer information" for more than 14 days.
We're hoping your issue is actually solved, and that you just forgot to tell us about it 
In order to keep our support team's screens tidy, we are marking this issue as closed.
Please do not hesitate to re-open it, should you need more support or details about it !

Best regards,

The Magnolia Support.

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