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
Of course this won't work because it isn't in any workspace it should have /en/edit/... .
I think more people will be running in this issue. Is it possible to make the workspace configurable in the React component. When we're on a English frontend page it should open the preview url in the English workspace: studio.url/en/edit/...
When we're on a French part of the frontend it should open in studio.url/fr/edit/...
I can see more scenarios where this will be needed. Not only for when people use the workspaces as translations but also for when content from multiple workspaces is being used on the same frontend. This issue will occur too.
The text was updated successfully, but these errors were encountered:
Currently we are using the workspaces as a way to manage content in different languages. Example here:
These workspaces live in certain urls in the sanity studio for the English workspace studio.url/en , for the French one studio.url/fr , etc...
This means when using the visual editor and clicking 'open in studio' it will open this url:
https://studio.url/intent/edit/mode=presentation;id=8541491f-4362-494c-b832-6fe256929c0a;type=contentPage;path=intro.intro%3A696f917f80d5.children%3Ab30f4b1d1ae42.text?baseUrl=https%3A%2F%2Famexio-fuse.sanity.studio&id=8541491f-4362-494c-b832-6fe256929c0a&type=contentPage&path=intro.intro%3A696f917f80d5.children%3Ab30f4b1d1ae42.text
Of course this won't work because it isn't in any workspace it should have /en/edit/... .
I think more people will be running in this issue. Is it possible to make the workspace configurable in the React component. When we're on a English frontend page it should open the preview url in the English workspace: studio.url/en/edit/...
When we're on a French part of the frontend it should open in studio.url/fr/edit/...
I can see more scenarios where this will be needed. Not only for when people use the workspaces as translations but also for when content from multiple workspaces is being used on the same frontend. This issue will occur too.
The text was updated successfully, but these errors were encountered: