[SOLVED] Reference field in scheme stopped suggesting available schemas

I have…

  • [x] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

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

Current behavior

The current version shows this in reference field schemas.field.references.query a believe there was select component with suggestion but I am not completely sure. But it definitely suggests schemes as the current version is prone to error.

edit: this is how its look for componet

Minimal reproduction of the problem

Create app with 2 schemas and then in one add field reference and try to set schema (type).


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

Version: 7.8.2


  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [x] Brave

The bug is the wrong translation key that is used here:

1 Like

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