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
When using a front-end framework to re-send the token back to GraphQL for live preview, if you have caching enabled, it's going to serve the cached response each time and not show the live preview edit.
You could send the statamic-live-preview random string to the URL as well, but the default GraphQL cache driver doesn't look at the query string.
How to reproduce
Enable GraphQL caching
Hit a GraphQL endpoing with a live preview token
Update the entry in live preview
See no change
Logs
No response
Versions
3.3.0 beta 3
Installation
Other (please explain)
Additional details
DefaultCache's getCacheKey should probably include all the query string variables in the key.
Also, we should just disable caching if it's a tokenized request.
The text was updated successfully, but these errors were encountered:
jackmcdade
changed the title
3.3 GraphQL queries with token shouldn't be cached
3.3 beta – GraphQL queries with token shouldn't be cached
Mar 3, 2022
Bug description
When using a front-end framework to re-send the token back to GraphQL for live preview, if you have caching enabled, it's going to serve the cached response each time and not show the live preview edit.
You could send the
statamic-live-preview
random string to the URL as well, but the default GraphQL cache driver doesn't look at the query string.How to reproduce
Logs
No response
Versions
3.3.0 beta 3
Installation
Other (please explain)
Additional details
DefaultCache's getCacheKey should probably include all the query string variables in the key.
Also, we should just disable caching if it's a tokenized request.
The text was updated successfully, but these errors were encountered: