search

sanity-io / sanity

Sanity Studio – Rapidly configure content workspaces powered by structured content
https://www.sanity.io
MIT License
5.33k stars 431 forks source link

Issue with the Portable text editor #5263

Open WebShapedBiz opened 1 year ago

WebShapedBiz commented 1 year ago

Describe the bug

A few days back, I was presenting the Sanity-based project to my client. We were in the conference room each having a laptop and both logged in to the same Studio Cloud at our-project.sanity.studio. My role was administrator and the client's was write.

When showing them how to create a Post, I saw that while my portable text editor looked as it should have, the client's editor showed only the Styles dropdown and the rest of the top bar, where there should have been Lists, Marks, Image and Youtube embed, was empty. The editor worked fine for both of us, there were no errors being displayed, only that the client didn't have most of the tools in the portable text editor.

Which versions of Sanity are you using?

@sanity/cli (global)          3.20.0 (latest: 3.20.1)
@sanity/cli                   3.20.0 (latest: 3.20.1)
@sanity/eslint-config-studio   3.0.1 (up to date)
@sanity/vision                3.20.0 (latest: 3.20.1)
sanity                        3.20.0 (latest: 3.20.1)
media-plugin         2.2.4

What operating system are you using?

I have elementaryOS 6.1 (based on Ubuntu 20.04.6) and the client was using a Windows 10 laptop.

Which versions of Node.js / npm are you running?

npm version: 10.2.1
node version: v18.18.0

Cheers.

mikeyfarina commented 6 months ago

hey @WebShapedBiz did you ever resolve this? Just began running into the same issue where the marks seemingly randomly stopped showing up - looks like a css flex box type issue, but i have no way to fix that on my end.

WebShapedBiz commented 6 months ago

Hi @mikeyfarina. This was a tough one to reproduce. I have never seen it on any of my computers, only that one time on my client's computer. The client has never reported that issue back to me so, to be honest, I thought that bumping Sanity to the current version (3.38.0) through time resolved it at some point. I'm sorry to hear that the issue is still here and that I couldn't do more for you.

Cheers.