Error in starter project causes studio to become inaccessible

Hey 👋I’m playing around with the starter project
Lifestyled: Editorial and E-Commerce and I’ve encountered an error making the studio inaccessible.I was playing around in the studio trying to remove some linked elements I believe and then it crashed.
As the error says there’s something with the multiple list items with the same ID, but I’m not sure what the
linked docs wants me to do. Can anyone lead me on the right path?Also, am I supposed to make my own error handling so that this kind of problem doesn’t occur, or is there something out of the box? If the studio was still accessible a content creator could fix it by setting the right linked elements instead of needing a software developer to fix it, so that would be optimal.

I don't think that is ever supposed to happen unless you duplicate an entry using the API.

Do you recall what you did right before this happened? We're pretty robust when it comes to elegantly handling errors and you aren't supposed to be able to break the UI with any editing actions, unless there's a brittle configuration.

I’m very happy to hear that you shouldn’t be able to break the UI! It didn’t seem right to me at all.
I didn’t do anything through through the API. I had done some simple actions in the UI. In this starter example there’s some linked elements and I went to remove the linked

askDorian

in the subcategories.
I’ll try and spin a new project of the same up again and see if I can replicate it

We’re also investigating on our end

Do you want me to grant you access to the project if that can help you in any way?

Thank you! Someone will be in touch on DM if that would be helpful.

Hi Casper, thanks for reporting this issue. We were able to reproduce it on our side as well now.
In its custom desk structure, the starter generates list item IDs from its subsection titles. This means that if the same title exists in a draft + published version of the same doc, or in two different documents, you'll end up with duplicate list item IDs.

Could it be that you might have edited or duplicated the subsection named "Ask Dorian" right before the error started happening?

We'll fix this in the starter itself, but to avoid having to start from scratch, you could make these changes to your

/src/deskStructure.js

file:
1. On line 22, replace this:

With this:

2.
After line 66:
Add this:

Please let me know if anything's unclear or the line numbers don't correspond for you
🙂

Thanks for the help, Peter! I can access the studio again.Now that I can see the studio I can better trace my steps; I believe I removed “Ask Dorian” from “Behind the scenes with Dorian” under Style > Ask Dorian. And then I also edited “Ask Dorian” under Subsection options. I’m not entirely sure what caused it to crash though.

Since I’m still new to Sanity and have only been playing around with this starter project for ~5 min. I can’t really say whether or not this is a common problem, but it seems rather easy to run into if several content creators are playing around in the studio? Or is it just because of this specific setup?
mentioned that you’re not supposed to be able to break the UI, but am I supposed to set additional “security” up so this doesn’t happen?Sanity seems great but it concerns me that the studio can become inaccessible like that.

It was an issue with the configuration of the starter that made it prone to this. We’ve now fixed it so it won’t happen to anyone else. I myself have never seen this exact error before.

Okay, that was also my understanding. It’s reassuring you haven’t encountered it before. I guess it’s just unlucky that I bump into it during the first project I play around with.Thanks for the quick help!

No problem – thanks for letting us know so we could fix it upstream! 🙇‍♂️