[SOLVED] pickContents show "NO SCHEMA"

I’m submitting a…

  • Regression (a behavior that stopped working in a new release)
  • Bug report ?
  • Performance issue
  • Documentation issue or request

Current behavior

I try to make custom editor and currently struggling with “pickContents”

I tried this example and it always “NO SCHEMA”

https://raw.githubusercontent.com/wild-card-ai/squidex-cms/24782bd550b5346bc9f92aa164d512e7822d1303/backend/src/Squidex/wwwroot/scripts/editor-dialogs.html

In my version i tried manually hardcode schemaId or schemaName both result in same.

Is there anything I missing or is there any docs covering this?

Expected behavior

Show proper dialog.

Minimal reproduction of the problem

Used same example with any field.

Environment

  • Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: latest/cloud

Browser:

  • Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge

I will have a look, tbh. I am not so sure right now. It is not an often needed feature.

1 Like

Base on my research, the issue is with the “components” field.

Some context:
I have field “contents” composed from basic blocks (component) like “component-text, component-image, component-show-some-reference-in-nice-ui etc…”. Currently it is based on default squidex components fields which fine for general use but i want to build kind of WYSIWYG editor base on tiptap.dev. And everything seems to be doable except picking references.


Mostly likely because my editor has to be set on “components” filed squidex is checking “allowed” references for “this” field and to not take in consideration that allowed component can have “allowed” references.

Proposed solution:
a) Introduce an option to skip the check and just show the requested schemas.
b) Somehow check for “allowed” references for each component.

I have fixed it, will be merged within the next hour.

1 Like

Awesome, I did a quick test with the latest dev Docker image, and it seems to work.

1 Like