-
Notifications
You must be signed in to change notification settings - Fork 471
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FTM: Future Contentlet Image Not Updating Correctly #31480
Comments
valentinogiardino
added a commit
that referenced
this issue
Mar 12, 2025
valentinogiardino
added a commit
that referenced
this issue
Mar 12, 2025
valentinogiardino
added a commit
that referenced
this issue
Mar 12, 2025
3 tasks
valentinogiardino
added a commit
that referenced
this issue
Mar 13, 2025
valentinogiardino
added a commit
that referenced
this issue
Mar 13, 2025
valentinogiardino
added a commit
that referenced
this issue
Mar 13, 2025
valentinogiardino
added a commit
that referenced
this issue
Mar 13, 2025
valentinogiardino
added a commit
that referenced
this issue
Mar 13, 2025
valentinogiardino
added a commit
that referenced
this issue
Mar 13, 2025
3 tasks
Passed QA! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
No response
Problem Statement
The issue with switching images between Draft, Preview, and Published states appears to be resolved; however, a new problem has been observed.
When viewing contentlets, the correct titles are displayed, and the initial image loads correctly. However, there is an issue when handling future contentlets with scheduled publish dates.
Steps to Reproduce
Expected Behavior:
• The future contentlet should display Image2 as it is the image associated with the scheduled version.
Actual Behavior:
• Instead of showing Image2, the old Image1 remains visible when previewing the future state.
Screen.Recording.2025-02-25.at.7.51.43.PM.mov
Acceptance Criteria
We should see the proper image assigned to the contentlet version
dotCMS Version
current main
Proposed Objective
Customer Success
Proposed Priority
Priority 1 - Show Stopper
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: