[DEFECT] Resource Links: `configuredImageURL` returns the wrong image
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
When a contentlet has multiple binary fields with different images, the Resource Links API returns a unique configuredImageURL for each field. However, all of those URLs display the same image, instead of the correct image for each field.
Steps to Reproduce
-
Create a Content Type with two Binary fields:
image1,image2. -
Create a contentlet of that type and upload two different images.
-
Request the endpoint:
/api/v1/content/resourcelinks/field/{field}for both
image1andimage2. -
Notice that although each
configuredImageURLis different, both URLs display the same image.
Video
https://github.com/user-attachments/assets/494954f6-27ff-4638-b18b-da50b7cab64b
Acceptance Criteria
- Each binary field should generate a
configuredImageURLpointing to its correct image. - The Resource Links API must consistently resolve field-specific image URLs.
External Links
https://dotcms.freshdesk.com/a/tickets/31305
dotCMS Version
main / trunk
Severity
Medium – Some functionality impacted.
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
Start by reproducing the Resource Links API request for two binary fields with different images, then trace how field-specific configuredImageURL values are resolved. Done means each returned URL consistently displays the image belonging to its requested binary field.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100