Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Drupal.quickedit.metadata doesn't refresh the SessionStrage data on node edits.
24 hrs left: https://d2zvu.ply.st/node/1
Reproduce:
1. Create a node.
2. ensure the quickedit is loaded from ajax ( so you may click the quickedit button, and need not to do anything)
2. edit a node with diff title and content
3. reload and use quickedit to hover the title/content.
(Even after editing with quickedit, the SessionStrage didn't refresh)
| Comment | File | Size | Author |
|---|---|---|---|
| c20171009_170136.png | 14.39 KB | droplet |
Comments
Comment #2
wim leersReproduced.
Comment #3
wim leersTo fix this properly, we need to have client-side cache tag support (cache tag invalidations on the server synced to the client). That's a much bigger general undertaking though. For now, we could fix this by
data-quickedit-entity-changedattribute that contains the last changed time of an entity (for entities that implement\Drupal\Core\Entity\EntityChangedInterface). We could choose to only allow client-side caching of entity data for entity types that implement that interface.This seems like such an obvious oversight, I wonder how everyone (and myself especially) overlooked this all this time?!
Comment #12
spokjeDue to Quickedit being moved out of Drupal Core and into a Contrib Module, moving this issue to the Contrib Module queue.