dotCMS / dotCMS/core

After CSV import, "Last Editor" not updated and imported values revert to old data

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

Nobody has claimed this yet.

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

Description

Problem Statement

After importing content via CSV, updated values appear correctly in the list view, but:

  • The "Last Editor" name and modification date are not updated (still show the prior editor/date).
  • In the detail view popup, the values do not update at all — they continue to display the older data.
  • After a period of time, values across the system revert to the old (pre-import) data.

This points to an import write path that isn't updating editor/mod metadata and/or a cache/index consistency problem where imported values aren't durably persisted (later overwritten by stale cached/indexed data). This is a data-integrity concern — imports appear to succeed but silently revert, undermining trust in bulk import.

Steps to Reproduce

  1. Import content updates into an existing content type via CSV.
  2. Check the list view — updated values appear correctly.
  3. Check "Last Editor" name/date — not updated (shows prior editor/date).
  4. Open the detail view popup for an updated item — shows old values.
  5. Wait a period of time — values across the system revert to the pre-import data.

Acceptance Criteria

  • CSV import updates the "Last Editor" name and modification date to reflect the import.
  • Updated values are consistent across list view and detail view immediately after import.
  • Imported values persist and do not revert after cache/index refresh.

dotCMS Version

Evergreen

Severity

High - Major functionality broken

Links

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

Start by tracing the CSV import path for existing content, then compare how the list view and detail view read the updated item. Reproduce the issue with an existing content type and verify the Last Editor, modification date, and values immediately after import and after cache/index refresh. Done means all stated acceptance criteria hold.

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
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.