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 creating new content we use hash routing like http://localhost:3000/#add/pages/test - not the actual path that the content will eventually live at.
This is because we don't necessarily know what the full path is going to be when first adding the content. We allow for route overrides that use :field() to get value from the content source, so those values wouldn't have been created yet.
After the first save of new content, we should compute the path and redirect to it. doing a hard refresh from there is still a race against the CI clock, but it's probably better than staying on the hash which is always expecting to be starting from scratch on reload.
The text was updated successfully, but these errors were encountered:
We are also trying to redirect on edit if the evaluated route changes. This is most common if you're using replacement patterns from your content fields, and you change one of the computed field values. If folks run into weird issues because of this, please let me know!
When creating new content we use hash routing like http://localhost:3000/#add/pages/test - not the actual path that the content will eventually live at.
This is because we don't necessarily know what the full path is going to be when first adding the content. We allow for route overrides that use
:field()
to get value from the content source, so those values wouldn't have been created yet.After the first save of new content, we should compute the path and redirect to it. doing a hard refresh from there is still a race against the CI clock, but it's probably better than staying on the hash which is always expecting to be starting from scratch on reload.
The text was updated successfully, but these errors were encountered: