-
Bug
-
Resolution: Won't Fix
-
Critical
-
None
-
2.4, 2.4.3
-
paas sl3
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.
Acceptance criteria
