dotCMS / dotCMS/core

Binary/image field not displayed after populating content into another language, until content is saved and republished

Open
#36,707 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : Customer Support Team : Maintenance
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Problem Statement

When creating a new language version of a contentlet via "Populate [language] content with [source language] content," all fields are copied — but a binary (image) field renders as an empty upload dropzone on screen, even though the field's value has in fact been copied. The image only becomes visible in the UI after the version is saved and the content is republished/reopened.

Steps to Reproduce

https://drive.google.com/file/d/1slH1BfiwwU-6641coLCfHWtDxlZRRQcM/view?usp=drive_link

  1. Open a contentlet with a binary/image field in its default language (e.g. Blog Author, Profile Photo field) — confirm the image displays.
  2. Switch to a second language in the Language panel.
  3. Click "Yes" on the "Populate [language] content with [source] content?" prompt.
  4. Observe: text fields show copied values; the binary/image field shows an empty "Drag and Drop or Choose File" dropzone.
  5. Click Save/Publish.
  6. Observe: dropzone still appears empty immediately after save.
  7. Close and reopen the contentlet in that language.
  8. Observe: the image now displays correctly.
Acceptance Criteria

Expected: The binary field should render the copied image immediately after populate, and continue to display it after save — without requiring a reopen.

dotCMS Version

24.12.27v24
26.07.06-02

Severity

Medium - Some functionality impacted

Links

https://dotcms.freshdesk.com/a/tickets/38354

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in the contentlet editor using the linked recording and the listed language-population steps. Start by tracing the populate-language flow and binary/image field rendering; done means the copied image appears immediately after population and remains visible after save without reopening.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
content, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.