sveltia / sveltia-cms

Alternative to Netlify/Decap CMS. Fast, lightweight, Git-based headless CMS. Modern UX, first-class i18n support, open source & free. Made with Svelte.
MIT License
862 stars 43 forks source link

getting an error trying to save edits in production... #158

Closed rchrdnsh closed 3 months ago

rchrdnsh commented 3 months ago

Getting the following error dialog when trying to save an edit to a collection entry on the live site:

Screenshot 2024-06-06 at 1 30 51 PM

It happens in production for multiple people...

it seems to happen for all collections

Here are the errors in the console:

Screenshot 2024-06-06 at 1 35 24 PM

and expanded:

Screenshot 2024-06-06 at 1 36 14 PM

I hope that helps :-)

kyoshino commented 3 months ago

Hmm, my quick test doesn’t reproduce the error. Do you see any error in the Network tab? A normal response would look like this:

image
rchrdnsh commented 3 months ago

this is the network info I am getting when I click save...

There are two graphql's that are created...

The first one is this:

Screenshot 2024-06-06 at 2 35 42 PM

and the second one is this:

Screenshot 2024-06-06 at 2 34 17 PM

I do not really understand them myself, but hopefully this helps :-)

kyoshino commented 3 months ago

Can I see the Preview tab next to Payload?

rchrdnsh commented 3 months ago

aha!!! under the preview tab I figured out i somehow had the wrong repo name...i fixed it and it worked!!! schweet :-) Thank you for guiding me

kyoshino commented 3 months ago

This is interesting, actually. If the config file has a wrong repo name, you should get an error while fetching data at startup. Not sure why it’s not the case 🤔

Maybe just a difference between the upstream and a fork?