[SOLVED] Singleton content sync errors

HK1 · July 28, 2021, 9:55am

I have…

[x] Read the following guideline: https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support. I understand that my support request might get deleted if I do not follow the guideline.

I’m submitting a…

[ ] Regression (a behavior that stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Documentation issue or request

Current behavior

Hello,

When running sq sync in folder we are getting failed: Singleton content cannot be created errors. Would it be possible to get some more context on what this error means, and how to prevent it? Looking at the code below it seems that the relevant condition failing is coming from context.ContentId != context.Schema.Id but it would be great to find out what exactly ContentId and Schema are so we can fix this.

Thanks

github.com

Squidex/squidex/blob/6dc7ca4d3807c654be04aad47ba067c269851979/backend/src/Squidex.Domain.Apps.Entities/Contents/DomainObject/Guards/SingletonExtensions.cs#L25


public static class SingletonExtensions
{
    public static void MustNotCreateForUnpublishedSchema(this OperationContext context)
    {
        if (!context.SchemaDef.IsPublished && context.SchemaDef.Type != SchemaType.Singleton)
        {
            throw new DomainException(T.Get("contents.schemaNotPublished"));
        }
    }

    public static void MustNotCreateSingleton(this OperationContext context)
    {
        if (context.SchemaDef.Type == SchemaType.Singleton && context.ContentId != context.Schema.Id)
        {
            throw new DomainException(T.Get("contents.singletonNotCreatable"));
        }
    }

    public static void MustNotChangeSingleton(this OperationContext context, Status status)
    {
        if (context.SchemaDef.Type == SchemaType.Singleton && (context.Content.NewStatus == null || status != Status.Published))

Expected behavior

Error message explaining what the problem is

Minimal reproduction of the problem

sq sync in folder

Sebastian · July 28, 2021, 11:02am

Yes, you are right. Singletons are not handled / covered by the CLI yet.

HK1 · July 28, 2021, 12:21pm

OK good to know, what exactly is a singleton so we can avoid this error? Couldn’t find anything in the docs.

Sebastian · July 28, 2021, 12:23pm

A singleton is a schema that has only one content item. This content item must have the ID of the schema it belongs to.

So when you make a sync to a new app, a new schema is created with a new ID. Therefore the content ID does not match to the schema ID anymore.

I will provide a fix for that soon. It will and can be solved in the CLI.

HK1 · July 28, 2021, 12:56pm

Great - any idea on when that might be fixed?

Sebastian · July 28, 2021, 1:19pm

Today, I hope…but I do not promise it.

Sebastian · July 28, 2021, 2:23pm

It has been pushed and deployed.

HK1 · July 29, 2021, 10:20am

Running the sync we are still getting the same error unfortunately. By the way we are using cloud squidex, the screenshot shows that we are currently getting served an old snapshot so that might be why we’re not seeing the change yet? Looking at the source and changelog I don’t see any recent updates.

Thanks

Sebastian · July 29, 2021, 12:33pm

Have you downloaded the new CLI?

HK1 · July 29, 2021, 2:49pm

Not yet, will give that a go.

system · July 30, 2021, 2:23pm

This topic was automatically closed after 2 days. New replies are no longer allowed.