Content disappears in intermediate dates when using time-machine
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
The time-machine feature allows visualizing content based on publish and expiration dates. Under normal circumstances, the current content should remain visible until the scheduled new version reaches its publish date.
Problem
In certain edge cases, a content item that is scheduled to be published at a future date is displayed correctly when that future date is selected. However, when navigating back to visualize the original content (the one that should remain active until the new version replaces it), the original content disappears in the intermediate dates between:
• Now (current date), where the content is visible.
• Future publish date, when the new version is supposed to appear.
So far, this problem can only be reproduced here using the main index page
Steps to Reproduce
- Create content A and set it as published (visible now).
- Edit content A and create a new version (A’) with a future publish date.
- Use Time Machine to navigate to:
• Current date → content A is shown ✅
• Future publish date → content A’ is shown ✅
• Intermediate date between current and future publish date → no content is shown ❌
Acceptance Criteria
Expected behavior
• Content A should remain visible up until the exact publish date of content A’.
Actual behavior
• In the intermediate window, neither A nor A’ is shown, creating a visibility gap.
dotCMS Version
current main
Severity
Critical - System unusable
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 issue through Time Machine on the main index page, following the listed current, future, and intermediate date steps. Compare the content visible at each date and verify that content A remains visible until the exact publish date of A’.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100