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 editing the body field (rich text / block content) in Sanity Studio, changes are not consistently detected. Occasionally, the yellow "unsaved changes" indicator does not appear after editing text in the body field. This causes content to be lost if the document is saved without the field being recognized as changed. In some cases, multiple attempts are required before changes are acknowledged.
Expected Behavior:
When text is entered or edited in the body field, the yellow "unsaved changes" indicator should consistently appear, and changes should reliably save upon hitting "Publish."
Actual Behavior:
The "unsaved changes" indicator sometimes fails to appear for the body field. This leads to loss of data when refreshing or navigating away, as the content does not save reliably.
Troubleshooting Steps Taken:
Confirmed that the body field is configured correctly as a block content array in the schema.
Updated Sanity Studio to the latest version.
Tried in multiple browsers and in incognito mode.
Disabled any plugins and cleared the browser cache.
The text was updated successfully, but these errors were encountered:
When editing the body field (rich text / block content) in Sanity Studio, changes are not consistently detected. Occasionally, the yellow "unsaved changes" indicator does not appear after editing text in the body field. This causes content to be lost if the document is saved without the field being recognized as changed. In some cases, multiple attempts are required before changes are acknowledged.
Expected Behavior:
When text is entered or edited in the body field, the yellow "unsaved changes" indicator should consistently appear, and changes should reliably save upon hitting "Publish."
Actual Behavior:
The "unsaved changes" indicator sometimes fails to appear for the body field. This leads to loss of data when refreshing or navigating away, as the content does not save reliably.
Troubleshooting Steps Taken:
Confirmed that the body field is configured correctly as a block content array in the schema.
Updated Sanity Studio to the latest version.
Tried in multiple browsers and in incognito mode.
Disabled any plugins and cleared the browser cache.
The text was updated successfully, but these errors were encountered: