Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translations Display fails #8789

Closed
3 tasks done
danieljwestman opened this issue Oct 14, 2021 · 3 comments
Closed
3 tasks done

Translations Display fails #8789

danieljwestman opened this issue Oct 14, 2021 · 3 comments
Assignees

Comments

@danieljwestman
Copy link
Contributor

Preflight Checklist

Describe the Bug

Not possible to choose the Translations Display:

Screenshot of People Translations

Error:

Skärmavbild 2021-10-14 kl  11 55 25

To Reproduce

Create translations for a collection, add a simple text field and try to choose the display "Translations".

What version of Directus are you using?

v9.0.0-rc.96 (with latest commit oct 14)

What version of Node.js are you using?

14.16

What database are you using?

PG 13

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying Directus?

Clone / running locally / NPM

@Nitwel
Copy link
Member

Nitwel commented Oct 14, 2021

I wasn't able to reproduce this. The only way this could happen is when the collection prop isn't set for the display but this is never the case for me. Thoughts @rijkvanzanten on a case where props wouldn't be set?

@rijkvanzanten
Copy link
Member

Not seeing it on my end neither..

Thoughts @rijkvanzanten on a case where props wouldn't be set?

Not really! These display options are rendered exclusively in the field management drawer, which is always a sub-route of the collection detail page, so it should be there no matter what.

I'll close this for now, as it'll be very difficult to keep track of what exact commit this might've happened on, seeing there's a bunch of commits every day. Down to keep discussing here though @danieljwestman 🙂

@Nitwel
Copy link
Member

Nitwel commented Oct 15, 2021

This was the same bug as in #8831 / got fixed by #8844

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants