You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are 2 related but maybe independent issues in this report:
After saving a document with drafts disabled (or publishing a document with drafts enabled), the value of useField({path: 'updateAt'}) remains outdated until you reload the page. This is a regression from v2 or an earlier v3 version.
1.Outdated.useField.path-.updateAt.mp4
In collections with drafts enabled, the "Last Modified" date shoes the modification of the published version, not of the draft. I would expect to see the modified date of the version that is currently being displayed.
Describe the Bug
There are 2 related but maybe independent issues in this report:
useField({path: 'updateAt'})
remains outdated until you reload the page. This is a regression from v2 or an earlier v3 version.1.Outdated.useField.path-.updateAt.mp4
2.Last.Modified.shows.published.at.mp4
Link to the code that reproduces this issue
https://github.com/payloadcms/payload/compare/franciscolourenco:reproduce-updated-at
Reproduction Steps
1. Outdated
useField({path: 'updateAt'})
updatedAt
value unexpectedly didn't change in the custom componentupdatedAt
value is now correct in the custom component2. "Last Modified" displays modification date of published document instead of draft
Which area(s) are affected? (Select all that apply)
area: ui
Environment Info
The text was updated successfully, but these errors were encountered: