I’m changing some things in my posts model to start using translations.
In the content table for posts I can get the title from Translations → Title, and it displays fine.
But in super header I can add the field just fine, but it just displays – for the title.
Any ideas?
Edit 1: I see now the warning that the header title only supports root level fields and not relational ones, stupid me, hope this is supported soon.
Edit 2: As far as I understand this should now be supported in v1.2 of Super Header. So I’ve opened an issue: Super Header - Relational fields not working? · Issue #206 · directus-labs/extensions · GitHub
1 Answer
1
Nice one and welcome to the community
!
Thanks for adding the issue. That’s definitely confusing as hell on our part (well my part mostly since I built that extension
)
So v1.2 DOES support relational fields. The note that it doesn’t inside the UI is just an oversight and needs to be removed.
On to the question of translations support for the title or subtitle displays…based on your account it seems like we need to take a deeper look at that. It should work because translations are just relationships too, but they’re also a bit special in how they’re treated.
Thanks again for adding the issue and we’ll look into it.
I ran into the same issue—also discussed here: https://github.com/directus/directus/discussions/19761 and https://community.directus.com/t/best-practice-for-displaying-translated-titles-in-directus-collections/749. Translated relational values didn’t show in list or detail view—maybe only certain setups work. The old docs (https://docs.directus.io) were more detailed in some areas. A proper update feature for Marketplace extensions would be great—I had to uninstall and reinstall Super Header manually.
– torbenhammes