🔮 Sanity Create is here. Writing is reinvented. Try now, no developer setup

Issue with portable text editor not showing anything, fixed by upgrading the desk client.

20 replies
Last updated: Apr 23, 2024
Has anyone experienced an issue where the portable text editor shows nothing? We've made no changes to our site but all of a sudden nothing is in the text editor bar.
Apr 17, 2024, 7:30 PM
Is your Studio embedded in a Next app?
Apr 17, 2024, 7:37 PM
user D
Wondering about RD’s question.
Apr 18, 2024, 2:35 PM
It is embedded, yep!
I was able to "fix" it by upgrading the desk client to the latest
Apr 18, 2024, 3:49 PM
Great! Glad to hear it.
Apr 18, 2024, 3:49 PM
I actually had to revert back to the prev sanity client (6.11.1) and structure (2.36.2) to keep things working properly. It broke both the rich text editor and the document search
Apr 19, 2024, 3:37 PM
Let’s use greetings like “Hey Everyone,” “Hi, Y’all," or “Hello, Folks” to make sure everyone in the community is included. Please read the Sanity Community Code of Conduct to stay updated on expected communication & behavior in our spaces: https://www.sanity.io/docs/community-code-of-conduct
Apr 22, 2024, 7:30 PM
Have you folks been seeing this anywehre else?
Apr 22, 2024, 7:30 PM
Looks like this deployed (left) and locally like (right)
Apr 22, 2024, 8:15 PM
user A
this is back and happening specifically in prod on our nextjs prod build. in dev it works OK. No console / browser errors.
Apr 22, 2024, 8:48 PM
What are you embedding it in? Can you share more details about your build?
Apr 22, 2024, 8:52 PM
This is within nextjs 14.2.0. Pretty standard config.

"use client";

import { NextStudio } from "next-sanity/studio";
import config from "../../../sanity.config";

export default function Studio() {
  return <NextStudio config={config} />;

// page
import Studio from "./Studio";

export const dynamic = "force-static";

export default function StudioPage() {
  return <Studio />;
Apr 22, 2024, 8:57 PM
Are there any errors in the console?
Also, as a side note, please do not DM team members here or on other platforms for assistance.
Apr 22, 2024, 9:05 PM
There are no errors within the console. No console / browser errors. Other notes: we use PNPM and Node v 20 if that matters!
Apr 22, 2024, 9:22 PM
I did DM knut, but only to share a code snippet / example that he asked for in replies that I couldn't publicly share
Apr 22, 2024, 9:27 PM
It’s odd that you mentioned there were no code changes before this started happening. Do you get the same behavior across different browsers?
Your best bet is to probably upgrade both Sanity and Next to their latest versions, delete node modules, reinstall, then redeploy.
Apr 22, 2024, 10:20 PM
Will give that a go! We did see it both in Safari and Chrome.
Apr 22, 2024, 10:22 PM
There was also a weird thing happening with styled components in the last few weeks that could be happening here. If what I suggested previously doesn’t work, try manually installing the latest version of styled components and do the whole reinstall/redeploy but again.
Apr 22, 2024, 10:29 PM
Ah, will give that a try as well.
Apr 22, 2024, 10:39 PM
Running NextJS 14.2.2, latest version of styled-components, latest sanity version 3.38.0, next-sanity 9.0.8, sanity client ^6.15
That finally worked
Apr 23, 2024, 2:00 AM
Heck yeah, brother!
Apr 23, 2024, 3:39 PM

Sanity– build remarkable experiences at scale

Sanity is a modern headless CMS that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.

Was this answer helpful?