Better locale handling in the collection overview #7382
yobottehg
started this conversation in
Feature Requests & Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We have a project with 3 languages.
Not all pages are translated in all languages.
The creation language is not the same in all content entries and also not the same as the fallback language.
This yields strange situations where a lot of entires in the "pages" collection overview page yield the term "no title":
I know that the locale selector at the top only set the users preferred language.
My authors translate this to their knowledge of other CMSs and understand this differently as a filter like on the website frontend.
They are confused with these entries and I don't see a way how to help them easily.
What the authors can do is to apply a filter on the page with "title" > "exists" > "true" which will hide the untranslated items.
However they should not do this all the time.
There is no hook to hide items in the collection overview based on the locale and going the "access control route" does not seem correct.
I found a way using the
beforeOperationHook
which replicates settings this filter internally with abusing the bouncerPattern a lot but this is error prone and ugly.I think something like this should be achievable easily and is also not so complicated. On the other hand I'm unsure if my case here is so special and no one wants / needs this?
Here my current hack if someone wants / needs this.
Beta Was this translation helpful? Give feedback.
All reactions