[DEFECT] Binary files do not carry over with all other fields when creating new language version.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
When using the "Yes" option in the dotCMS prompt for auto populating all fields with the default langauge on creating a new language version of a contentlet, the binary field does not carry over as it used to.
Steps to Reproduce
https://github.com/user-attachments/assets/8846f142-6443-4610-b5b4-7b6de4771a51
Acceptance Criteria
Ensure that Binary fields get carried over when a new language version is created and the "Yes" option is selected in the "Populate Confirmation" dialogue box.
dotCMS Version
Evergreen version 26.06.04-01
Severity
Medium - Some functionality impacted
Links
https://dotcms.freshdesk.com/a/tickets/37903
PR that may have introduced this bug. https://github.com/dotCMS/core/pull/35738
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 reviewing PR #35738 and the code behind the dotCMS "Populate Confirmation" dialogue when creating a new language version. Reproduce the issue by selecting "Yes" and verify that binary fields carry over along with the other fields; done means this behavior works for the reported Evergreen version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100