Search filter not working in one Directus instance

Help
1

Hello there,

i have a problem similar to the one described in this issue #6638 on Github.
Basically i can’t search anything in any collection in this one directus instance. I can see it working just fine in other instances though. So i know it is not a general bug.

grafik
grafik1771×840 19.7 KB

The directus version is 11.14.0, but it has been occuring multiple versions before already.
We use a Postgres database. All our Directus instances have been deployed through the Directus Template from Railway.

Since the problem is occuring in our large production instance, it would be very nice if it would be somehow fixable.

Oh and i also know for sure that the problem is not related to the schema or data-model. I have the identical schema in a testing instance and i am importing/exporting the schema through a plugin.
No such problems in the testing instance.

Note that i had to add a tag, but i didn’t find any tag that would fit. So please ignore the Data-Modeling tag. It has nothing to do with this question.

Cheers!

1 Answer

1
2

In case anybody is wondering. I found the issue and fixed it.

The “Searchable” propertiy of all fields had suddenly become undefined (neither true nor false).
This was and still is also the case for newly created collections/fields.

There must have been something to throw this particular directus instance off, because this is not happening anywhere else still.

It is no problem to work around this though. There is very few changes to the content model happening late in production anyway