[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: |
|
||||
| Issue Links: |
|
||||
| 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: | |||||
| Work Started: | |||||
| Description |
| 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: 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 ] |