[RESPDAM-98] Issue with Image Focal module in Magnolia 6.2.40 Created: 12/Dec/23  Updated: 15/Dec/23  Resolved: 15/Dec/23

Status: Closed
Project: DAM Focal
Component/s: commons
Affects Version/s: 2.4, 2.4.3
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Eduardo Galán Assignee: Raphael Falvo
Resolution: Won't Fix Votes: 0
Labels: cs-bk
Remaining Estimate: 0d
Time Spent: 1h
Original Estimate: Not Specified
Environment:

paas sl3


Attachments: PNG File image-2023-12-14-16-35-22-980.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:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Team: AuthorX
Work Started:

 Description   

Steps to reproduce

Any component that uses focal doesn’t display images if it is created after the update to 6.2.40, or if a component that was added previously is updated. Components that don’t use focal are unaffected.hots, gifs...

Expected results

Images can be added or updated without any error appearing. They should also be stored at JCR repository normally. 

Actual results

 

There are clear errors being output in the logs when accessing or saving the component.

2023-12-11T11:30:11.440244129Z 2023-12-11 12:30:11,439 WARN  ia.templating.imaging.VariationAwareImagingSupport: Supplied variation [240] could not be found. Please update your configuration.
...
2023-12-11 12:30:11,446 WARN  ia.templating.imaging.VariationAwareImagingSupport: Supplied variation [240] could not be found. Please update your configuration.
...
2023-12-11 12:30:18,938 WARN  ia.dam.templating.functions.DamTemplatingFunctions: The following ItemKey '' generated exceptions when trying to retrieve the associated Item:[ItemKey is null or blank.] at Node:[node /home/banner/0] Workspace:[website]
2023-12-11 12:30:18,938 WARN  ia.dam.templating.functions.DamTemplatingFunctions: The following ItemKey '' generated exceptions when trying to retrieve the associated Item:[ItemKey is null or blank.] at Node:[node /home/banner/0] Workspace:[website]

The failing images don’t appear to exist in the “images” JCR repo which is where focal appears to store it’s artifacts

Workaround

Development notes

The focal module version was 2.4, this has now been updated to 2.4.3 and unfortunately doesn’t seem help with this problem.



 Comments   
Comment by Eduardo Galán [ 14/Dec/23 ]

Hi rfalvo 

I've got some update on the issue from customer. They were working ok at magnolia 6.2.37 and focal module 2.4.0 and they starting to get the error after upgrading to 6.2.40 when they add or update images to components that use the focal module. If they revert to 6.2.37 the error doesn't appear. their literal comment is at https://jira.magnolia-cms.com/browse/HELPDESK-6068?focusedCommentId=389209&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-389209

I'll request logfiles from them to have further info on the error. In any case, if there's some specific doubt or point to detail on the reproduction of the bug let me now and I'll ask for it

Regards, Eduardo

Comment by Raphael Falvo [ 15/Dec/23 ]

It could be that customer is using webp images and issue would come from what is mentioned in the know issues of 6.2.40:

https://docs.magnolia-cms.com/product-docs/6.2/Releases/Release-notes-for-Magnolia-CMS-6.2.40/Magnolia-6.2.40-known-issues.html

I would advise them to either implement the workaround mentioned in the previous link or switch to 6.2.41 which has normally this fix already in place.

Comment by Raphael Falvo [ 15/Dec/23 ]

https://docs.magnolia-cms.com/product-docs/6.2/Releases/Release-notes-for-Magnolia-CMS-6.2.40/Magnolia-6.2.40-known-issues.html

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