-
Notifications
You must be signed in to change notification settings - Fork 2k
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
updatedAt
is not updated when saving drafts
#10436
Comments
franciscolourenco
added
status: needs-triage
Possible bug which hasn't been reproduced yet
validate-reproduction
labels
Jan 8, 2025
github-actions
bot
added
created-by: Contributor
and removed
validate-reproduction
labels
Jan 8, 2025
franciscolourenco
changed the title
Jan 8, 2025
updatedAt
is not udpated when saving draftsupdatedAt
is not updated when saving drafts
DanRibbens
added
status: verified
If an issue has been reproduced
and removed
status: needs-triage
Possible bug which hasn't been reproduced yet
labels
Jan 9, 2025
paulpopus
added a commit
that referenced
this issue
Jan 13, 2025
… when drafts are updated (#10503) Fixes #10436 Fixes an issue where drafts' updatedAt timestamp is not being updated. We weren't updating the `versionData` to have the right timestamp in the saveVersion operation when drafts were being updated. Added e2e tests to make sure 'Last Modified' is always different in both autosave and non-autosave drafts.
🚀 This is included in version v3.17.0 |
This issue has been automatically locked. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the Bug
The
updatedAt
field is not being updated when saving new drafts, only when publishing documents.Screen.Recording.2025-01-08.at.06.53.04.mp4
Link to the code that reproduces this issue
https://github.com/payloadcms/payload/compare/franciscolourenco:reproduce-updated-at-in-drafts
Test results
Reproduction Steps
updatedAt
field didn't changeAlso check included tests.
Which area(s) are affected? (Select all that apply)
db-mongodb, area: ui, area: core
Environment Info
The text was updated successfully, but these errors were encountered: