dotCMS / dotCMS/core

Copying a content with binary fields with same name files, duplicates files for all binary fields

Open
#24,135 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Problem Statement

If you create a content type with several binary fields, and for each of them you upload a diff file with the same name when copying the content it puts the same file (last one found) for all the fields.

Steps to Reproduce
  1. Create a content type with 3 binary fields and a title field.
  2. Create content with 3 diff images but all have to have the same name.
  3. Copy the content.
  4. Check that for all the fields are the same (this is the issue).

https://user-images.githubusercontent.com/5278970/219416727-6b706e47-246b-4d07-9aa2-032daf2bbce3.mov

Acceptance Criteria

When copying content we should maintain the files.

dotCMS Version

21.06 LTS and demo (23.01).

Proposed Objective

Customer Support

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

Customer ticket https://dotcms.zendesk.com/agent/tickets/110097

Assumptions & Initiation Needs

No response

Sub-Tasks & Estimates

No response

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

No source files or tests are named. Start by reproducing the issue with three binary fields and same-named files in the listed dotCMS versions, then trace the content-copying path. Done means each copied binary field retains its corresponding original file rather than sharing the last file found.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, content
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.