-
Notifications
You must be signed in to change notification settings - Fork 16
Description
Describe the bug
When configuring the integration for visual editing/presentation (per the readme), everything works great except for page navigations within Sanity's Presentation tab. When trying to navigate (via link or manually changing the URL within the Presentation view), the page does not reload. In order to see the page that was navigated to, the current Sanity studio page must be manually reloaded.
To Reproduce
Steps to reproduce the behavior:
- Set up the sanity-astro integration for visual editing per the readme (using
loadQuerydemo code from readme) - Stub out routes in Astro to render Sanity pages (can simply render page slug and raw JSON data, for demo purposes)
- Create multiple pages in Sanity
- Attempt to navigate between pages within Sanity's
Presentationview - Notice no page navigation occurs until the Sanity Studio page is fully reloaded manually (via browser refresh)
Expected behavior
Pages should reload/navigate automatically when the route is changed, per Sanity's presentation demos for other frameworks (e.g. Remix)
Screenshots
Initial view in Presentation of homepage:

Upon trying to manually change the route within Sanity Studio:

Note that data + page being rendered is still for homepage.
After browser refresh/full reload of sanity studio:

Correct data is now displayed
Which versions of Sanity are you using?
Run sanity versions in the terminal and copy-paste the result here:
@sanity/cli (global) 3.52.4 (latest: 3.53.0)
@sanity/eslint-config-studio 3.0.1 (latest: 4.0.0)
@sanity/vision 3.51.0 (latest: 3.53.0)
sanity 3.52.4 (latest: 3.53.0)
What operating system are you using?
Mac OS 13.6
Which versions of Node.js / npm are you running?
Run npm -v && node -v in the terminal and copy-paste the result here:
NPM: 10.2.3
Node: v18.19.0
Additional context
- Using the
Refreshbutton above the iframe pane in Sanity'sPresentationmode also does not have an effect - I am using server-side rendering within Astro, and running a dev server with
netlify dev - I notice the issue both locally, and when deploying both the frontend (to Netlify) and backend (to Sanity)
- I suspect the issue might have something to do with the
loadQuerydemo code provided in the readme, but I am not sure