[INACTIVE] Squidex CLI: failed: Invalid command

Bugs Stale Bugs
#1

I have…

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

We are trying to sync schemas and contents between two apps, but we are getting an error when trying to do so.

I’ve exported app-a with ./sq sync out ./test-a/ and trying to sync to app-b with ./sq sync in -t schemas -t contents ./test-a/. I’m just getting:

  • STEP 2 of 3: Importing contents started

Upserting #0… failed: Invalid command.
Upserting #0… failed: Invalid command.
Upserting #1… failed: Invalid command.

Any idea of what this is?

Expected behavior

I Expect that all the settings are synced to app-b without errors.

Minimal reproduction of the problem

Environment

  • [ x] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: 5.7.1
CLI Version: 7.8

Browser:

  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge
#2

Sounds like a bug that is already fixed.

#3

I’m on version 7.8 in the CLI?

#4

No, it is API issue.

#5

Oh. I will try that!

#6

Hi Sebastian.

I’ve updated Squidex to 5.8.0 and tryed again - Same result.

Here I’m doing the sync out command: https://pastebin.com/fUJPFwbx
and the sync in command: https://pastebin.com/2TTcft2f

There is also some funky things going on in Squidex after this.

If I’m doing the same sync in command again, it gives me this output:

  • STEP 0 of 3: Importing Assets started

Uploading 962a258e-bea3-448b-9e1f-f78…succeeded.
Uploading 2ebe352a-6841-4e89-9a1c-969…succeeded.
Uploading 2ebe277c-f92e-459c-9771-0cb…succeeded.
Uploading 0dc1e061-87c2-4f43-a7cb-f11…succeeded.
Uploading 99fbe6e4-18c4-48de-8dfa-241…succeeded.
Uploading 48695994-e86b-4ac0-8373-14f…succeeded.
Uploading 508b4d3b-93e0-459e-abb4-470…succeeded.
Uploading f1598e9a-d889-4e97-8d2a-816…succeeded.
Uploading 45a1cee4-7aec-4e1f-bdf3-341…succeeded.
Uploading 27380185-510d-4879-a95e-efe…succeeded.
Uploading 35bbef13-fdb8-44a3-9189-157…succeeded.
Uploading 87ff4b1c-5f1f-4d9f-a53d-ba1…succeeded.
Uploading c9be3b59-7ec1-4b14-b837-f04…succeeded.
Uploading 22e0f414-5a9e-471e-8bbf-836…succeeded.
Uploading c687e8f2-f1a4-448e-a966-db6…succeeded.
Uploading 49335374-350e-4411-abbe-fbd…succeeded.
Uploading a675435d-0945-4cb3-ba2b-78b…succeeded.
Uploading ef559ccc-783f-40cf-a2a9-24f…succeeded.
Uploading 88a68c9a-5dfb-4219-b3d1-9fc…succeeded.
Uploading 0e754980-225a-4488-800c-d5c…succeeded.
Uploading fea617b6-20f4-4b4f-ae5a-7a3…succeeded.
Uploading ae38eccd-e8c0-471c-98d0-6b6…succeeded.
Uploading 2398a581-2838-4ea4-88b8-a7c…succeeded.
Uploading 2e5d4367-f5e1-4cc3-8a2b-3ba…succeeded.
Uploading 44f285aa-1341-4851-b1f8-4e0…succeeded.
Uploading 673759c4-a776-4893-97b0-287…succeeded.
Uploading 056be38d-faa0-449e-9a7f-bc9…succeeded.
Uploading 8df0e65f-4de1-4646-9ff6-6ba…succeeded.
Uploading aa264c03-a559-4e1a-be85-65d…succeeded.
Uploading e4f06090-59b9-4037-bec0-5d4…succeeded.
Uploading 94e4b627-f203-449f-930d-579…succeeded.
Uploading 425cfc35-5742-4d44-ab26-b22…succeeded.
Uploading 9677579f-288e-45e7-a883-57a…succeeded.
Uploading a7713f1d-9a4c-4605-9ba7-1a6…succeeded.
Uploading b6328eca-8e9d-44b6-bafe-a6f…succeeded.
Uploading d323d5db-c65b-45c4-bafd-6b5…succeeded.
Uploading 8000b6d1-2648-490b-9fb6-032…succeeded.
Uploading 9511cc9c-a63e-4579-8479-5cb…succeeded.
Uploading f8100b55-16ec-487b-988c-dd9…succeeded.
Uploading 8ff6238c-0a08-4d6c-95e8-b70…succeeded.
Upserting #0… succeeded.
Upserting #1… succeeded.
Upserting #2… succeeded.
Upserting #3… succeeded.
Upserting #4… succeeded.
Upserting #5… succeeded.
Upserting #6… succeeded.
Upserting #7… succeeded.
Upserting #8… succeeded.
Upserting #9… succeeded.
Upserting #10… succeeded.
Upserting #11… succeeded.
Upserting #12… succeeded.
Upserting #13… succeeded.
Upserting #14… succeeded.
Upserting #15… succeeded.
Upserting #16… succeeded.
Upserting #17… succeeded.
Upserting #18… succeeded.
Upserting #19… succeeded.
Upserting #20… succeeded.
Upserting #21… succeeded.
Upserting #22… succeeded.
Upserting #23… succeeded.
Upserting #24… succeeded.
Upserting #25… succeeded.
Upserting #26… succeeded.
Upserting #27… succeeded.
Upserting #28… succeeded.
Upserting #29… succeeded.
Upserting #30… succeeded.
Upserting #31… succeeded.
Upserting #32… succeeded.
Upserting #33… succeeded.
Upserting #34… succeeded.
Upserting #35… succeeded.
Upserting #36… succeeded.
Upserting #37… succeeded.
Upserting #38… succeeded.
Upserting #39… succeeded.

  • STEP 0 of 3: Importing Assets completed
  • STEP 1 of 3: Importing Schemas started

Schema app-configs updating… skipped: Nothing changed.
Schema sites updating… skipped: Nothing changed.

  • STEP 1 of 3: Importing Schemas completed
  • STEP 2 of 3: Importing contents started

Upserting #0… failed: Invalid command.
Upserting #0… failed: Invalid command.
Upserting #1… failed: Invalid command.

  • STEP 2 of 3: Importing contents completed

Synchronization completed.

So I thought huh, maybe there is some assets now. But when I browse assets, there is none shown with the filter All tags - If i change the filter to image I can see the desired images.

Other folders I get some exceptions in the squidex backend. See logs here: https://pastebin.com/dHrVWcKa

#7

I will have a look, thanks … can you send me your export or database?

#8

Btw: Are you using custom IDs? The invalid command error could be because of that.

#9

We are not using custom IDs. I’ve sent you a backup of the app.

Thanks for your support, much appreciated!

#10

Can you also send me the folder that is created by the “sync out” command?

1 Like
#11

I cannot reproduce it. I need the database update with mongorestore (https://docs.squidex.io/01-getting-started/installation/troubleshooting-and-support#prepare-a-backup-of-your-mongo-database) and detailed instructions how to reproduce it.

#12

Sent you a dump of the squidex db and steps to reproduce.

#13

Hi @Sebastian
I am facing the same issue while sync in only content of a specific schema is giving me this failed:Invalid command.

#14

Is it a singleton schema?

#15

I looked into this and observed those content which have localizable those content are giving me error. Other language is Chinese(Zh)

#16

I think the only options to figure out what is going wrong are:

  1. You provide me a way to workaround this.
  2. You give me an export of your database and the source folder.