#Stale admin view

6 messages ยท Page 1 of 1 (latest)

final bone
#

Hello there ๐Ÿ‘‹ , I am encoutering some weird behaviour (payload 3.84.1 next@16.2.4) with the admin ui: unless i refresh, the admin ui's data is always one step behind. So when I make some modifications and save or publish the document, the admin ui somehow grab the version before I made the modifications ( cache issue with next 16 maybe ?), this is extermely annoying as everytime I save/publish modifications I have to refresh the page to make sure the data in the admin ui is the published one. Auto-saving is also a no-go since after I publish and the admin ui gets filled with stale data that gets auto-saved too ๐Ÿซ 

Could it be a templates mismatch, since I am using a next 15 template with next 16 ? I didn't see a migration guide to next 16 so I am assuming thats not the case, could be wrong though ๐Ÿ™‚
Can i have some advice on how to debug this ?

Thanks

pulsar pulsarBOT
final bone
#

Stale admin view

sick prism
#

I think you're on the right tracking thining it could be conflict with the old template using new next js version honestly

final bone
#

All right, will try to use the new template, hope it fixes the issue ๐Ÿ™

final bone
#

Apparently that was not the issue, after some digging I found issues for similar behavior, don't know what causes it specifically though:
https://github.com/payloadcms/payload/issues/14217
https://github.com/payloadcms/payload/issues/9012

GitHub

Describe the Bug Description In our Payload CMS project (Supabase/Postgres backend, deployed on Vercel), the Admin panel intermittently shows an old version of a document even after a newer version...

GitHub

Describe the Bug The Payload UI will at times show old data which can cause users to make changes to an older version of a document and publish over a newer version. Link to the code that reproduce...