Hi,
I've enjoying Directus so far, but one thing which I couldn't find any solution for is that when I'm "playing" around with fields and stuff, suddenly the list view doesn't show anything anymore, like below:

But if I click on it, I can clearly see the text:

And when this happens, I can rename and change stuff around as much as I want, it doesn't come back...
What is happening? Is this a bug or is this only some sort of misconfiguration?
Thanks in advance!
Directus 8.8.1
Ubuntu 16.04.7 LTS
MySQL Ver 8.0.22
Using the app inside Chrome 86.0.4240.111 x64
I've seen this happen sometimes where a relational field was setup incorrectly which in turn makes the API try to return it as a relational field instead of raw data. Could you try checking directus_relations in the DB for anything funny?
try checking directus_relations in the DB for anything funny
Yep, that solved it. It had a "loose" entry from a earlier relational "experiment" there. I deleted the suspicious entry (the entry with the field name) and it came right back :)
To future readers: If your field is NOT relational (if it's a normal text or dropdown field without any link to another table) and the field name appears inside the directus_relations table, it's a loose entry and you can delete it (You can access this table by enabling hidden tables inside Directus, or with your favourite SQL manager)
Since it's still a bug, should I close this issue or leave it open?
We can leave it open as it's technically a problem in v8. I've already tackled this in the upcoming v9 by not even allowing to setup relations to non-relational fields and making sure old relations get deleted when you delete a field 馃檪
We can leave it open as it's technically a problem in v8. I've already tackled this in the upcoming v9 by not even allowing to setup relations to non-relational fields and making sure old relations get deleted when you delete a field 馃檪
That's great news! Thank you so much for the incredibly fast response and for your help.
Directus, and everyone working on developing it (including you) are a godsend 馃挴
Keep up the great work :)
Most helpful comment
I've seen this happen sometimes where a relational field was setup incorrectly which in turn makes the API try to return it as a relational field instead of raw data. Could you try checking directus_relations in the DB for anything funny?