adobe / adobe/aem-core-wcm-components
Image not rendering when accessed via Embed component
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 796
- Forks
- 776
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 8
Description
Bug Report
Current Behavior
When I add an image dialog to the embed -> embeddable component, the image selected is not rendered but returns a 404 error. The ALT tag information is displayed. Upon inspecting the HTML, the SRC is captured within the image element.
Expected behavior/code
When I add an image dialog to the embed->embeddable component, the image selected should be rendered along with the other properties (HTML attributes) captured in the dialogs (cq:dialog,cq:design_dialogs...).
Environment
-
AEM version and patch level:
-
Core Components version : v3
-
JRE version:
Possible Solution
Additional context / Screenshots
Steps to Reproduce
-
Update the embed -> embeddable component to include the image dialogs/clientlibs.
-
Edit a page within AEM -> Sites
-
Add the embed component
-
Edit the embed component
-
Select the embeddable radio button
-
Select Image from the select field
-
Pick an image from the system
-
If needed, provide an ALT description
-
Click the Done button
-
Preview the page: The image does not appear.
HTML
Links
Embed Package
embed-package-troubleshoot-1.0.zip
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the attached embed-package-troubleshoot-1.0.zip, following the embed → embeddable image steps. Inspect the generated HTML and the request returning 404, then trace how the Embed component renders the selected image and its dialog properties. Done means the image renders in the page preview with its ALT and other captured attributes preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100