Cannot save or publish custom type

Prismic for Content Creators
1

Hi guys,

I have an issue where saving documents in Prismic tells me that there was an error and the document can't be saved. This seems to only happen for the new types I've created, so home and form_page.

Screenshot 2021-01-27 at 10.08.23
Screenshot 2021-01-27 at 10.08.23836×190 8.84 KB
Screenshot 2021-01-27 at 10.08.55
Screenshot 2021-01-27 at 10.08.55932×574 22.8 KB

If I try and query them I get nothing back - { error: null, slices: [] } - and in the graphql explorer I can't see the form page in the schema, and getting the number of documents returns - "totalCount": 0.

Some help would be great.

Thanks,
D

2

Hello David,

Welcome to the Prismic Forum.

We haven't reported this issue from our side. Are you still not able to save documents? If so, can you please share your repository url with me? You can send me a private message.

Thanks,

Priyanka

4

Hi Priyanka,

I've sent you a private message. Let me know if you need anymore info.

Thanks,
D

5

Hello David,

I've received your message. I'll let my developer team know about the issue and return to you when I hear back from them.

Thanks for your patience.

Priyanka

9

I am now receiving the same issue. This seems to be become a common problem. Have you found the deploy that has caused this issue?

10

Hey Patrick,

They told me on Friday (January 29th) they were rolling out some fixes but as of today, I still can't save or publish documents.

@Priyanka can we have some updates please?

11

Hello, @daveymoores @patrick4

Sorry for the inconvenience. There is a fix, but it still needs to test and deploy. I don’t have any hard ETA from the team on this. I'll update you all here once I hear back from my dev team.

Thanks,

Priyanka

12

Hi @Priyanka,

I don't have many models in my repository, so if the fix is to create a fresh repository that might be an option for me.

Can I understand what causes this issue and get an ETA on the fix so I can make a judgement as to whether I should wait, create a new repository or find a different headless cms and get a refund.

Many thanks,
D

13

Hello, @daveymoores

I apologize for the delay in the fix. As I informed in my previous thread that I don't have any ETA from the team.

You can surely create a fresh repository without any issues.

Priyanka

14

Thanks @Priyanka - can you resend that link? The above doesn't work.

D

20

Hello @daveymoores @patrick4

There is an update on this issue. It has been released. It should get fixed now.

Let me know if you are still getting the error.

Priyanka

21

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.