[RESPDAM-90] "Original" request sometimes returns not original image but image with minHeight/minWidth Created: 07/Aug/23  Updated: 15/Aug/23

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

Type: Bug Priority: Neutral
Reporter: Christoph Damm Assignee: Adrien Manzoni
Resolution: Unresolved 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   

Hello,

I have a weird issue with focal points for one of our clients.
When we request the original like this .imaging/focalpoint/original/dam/jcr:...../......

sometimes not the original is returned but a way smaller image. Height and Width are actually matching the min definitions of the ones from the first variation.

 

Variation definition e.g.:

variations: !override
  default:
    description: 16x9 Standard
    minHeight: 144
    minWidth: 256
    ratio: 16/9
    allowedWidths:
      - 256
      - 426
      - 640
      - 848
      - 958
      - 1024
      - 1262
      - 1280
      - 1600 

Also: we have 2 public instances for that client, and we have cases where the image within one instance is returned fine, within the other one not. Deleting the image from the imaging workspace sometimes resolves the issue, however this can't be a permanent solution.

We most likely will switch to not using the original anyways for other reasons, yet i have another issue with that (see RESPDAM-89), nevertheless wanted to log that issue here.

 

Regards,

Christoph



 Comments   
Comment by Raphael Falvo [ 15/Aug/23 ]

Hello chrisD ,

Could you please specify the version of Magnolia and the DAM Focal module in which you encountered this issue?

Comment by Christoph Damm [ 15/Aug/23 ]

Hi,

apologies. Magnolia 6.2.35 dx and dam focal 2.4.0.
We're also updating to 6.2.37 and 2.4.1, however i could not yet find a pattern when this would happen.

Comment by Raphael Falvo [ 15/Aug/23 ]

Hi chrisD 
Thank you for the feedback. Unfortunately, without a way to reproduce the issue, it will be challenging for us to conduct further investigation.
I can see that the most recent version of the image focal module is 2.4.2. I would recommend updating to this version as a first step and see if the issue is still coming up.

 

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