adobe / aem-core-wcm-components

Standardized components to build websites with AEM.
https://docs.adobe.com/content/help/en/experience-manager-core-components/using/introduction.html
Apache License 2.0
724 stars 737 forks source link

Featured Image: Console error when alt text is inherited from DAM #2578

Open nhirrle opened 10 months ago

nhirrle commented 10 months ago

Bug Report

Current Behavior 1.) Upload an image and configure the title in the metadata 2.) Create a page and open it. In Tab "Image" select that image as a "Featured Image". Select checkbox "Inherit value from the DAM asset". Save 3.) Open Browser console and refresh the page

Expected behavior/code Alt text is shown from the DAM Title in read only field.

Actual behavior/code 1.) The alt text is not shown 2.) A Network error with a 404 to /mnt/overlay/wcm/core/content/sites/undefined.htmlundefined is shown. 3.) Code which is producing it: https://github.com/nhirrle/aem-core-wcm-components/blob/b49e22c80a42b8db9c4804b8fe0b72e684cc48df/content/src/content/jcr_root/apps/core/wcm/components/image/v3/image/clientlibs/editor/js/image.js#L221 - thumbnailConfigPath returns undefined

Environment

ssteinerHLS commented 2 months ago

I created a support case through Adobe Admin Console with a similar behaviour (CASE ID E-001232084)

Page Property Featured Image: Alternative Text inherited from DAM asset not displayed anymore in author after reload

Current behaviour 1.) Edit Page Properties, Tab "Images" pick image as a "Featured Image". Select checkbox "Inherit - Value from the DAM asset". (Be sure to pick an image from DAM with a title or description text) 2.) "Alternative Text“ from DAM is visible in read only field. Save & Close 3.) Reopen Page Properties 4.) Navigate to Tab "Images“, field "Alternative Text“ is empty and field is not disabled/read-only

Expected behaviour "Alternative Text“ is shown from the DAM title or description in disabled/read-only field.

Actual behaviour "Alternative Text“ is empty and field is not disabled/read-only

Environment • Adobe Experience Manager 6.5.19.0 • Core Components version 2.23.4

Same behaviour with Adobe Experience Manager 6.5.20.0 and a locally built Adobe Experience Manager Core WCM Components Reactor 2.25.1-SNAPSHOT

Problem potentially in image.js: image/v3/image/clientlibs/editor/js/image.js

Screenshot 2024-05-06 at 17 08 35

ssteinerHLS commented 2 weeks ago

I just checked the state of this issue with the branch SITES-22027 of #2757 . I can confirm, this will fix this issue 🎉