[#18400] - RFC Language filters in admin UI
- Closed
- 24 Mar 2018
- Medium
- Build: staging
- # 18400
Currently we can filter things (eg articles and modules) in the admin UI with the language selector search tool.
However it works on an exclusive basis which can cause issues.
Example
I have a multilingual site (FR/EN) with some modules assigned to just one language and some modules assigned to all
Now if I only want to see the modules that will appear on EN pages I select english on the filter
Do you see the problem?
Hint the modules set to ALL will also appear on the EN pages and there is no way for me to display those modules in the same list.
Solutions
Possibility would be to
- Change the language select to include anything tagged ALL - eg Select FR and you see FR and ALL
- Change the language select to be a multiselect list eg Select FR and ALL
joomla-cms-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | Feature Request Multilanguage |
| Status | New | ⇒ | Discussion |
The point is that in order to see which modules appear on a French site I might have to filter by French first and then filter again by all.
Proposal 1 sounds logic. A site maintainer would like to know what is actually shown, which is chosen language and any potential All (should you have chosen to have such)
I think 1) is more logical, because all means also assigned to this language...
I agree with 1).
If anybody want to see only specified language modules then can sort by language field.
There is one big thing that puzzles me with option 1 :
Almost all my sites are multilingual. When do I filter for instance Articles or Menu Items on a language basis ? Typically when I want to select them all to batch-duplicate them into the second/third language.
Elements which are set to "all" are already good for "all" languages on the website and per definition don't need to be translated.
So proposition 1 would make life more complicated from that point of view.
But I would be happy with proposition 2, as there everybody gets exactly what she/he wants.
I'd go with option 2 simply because with option 1 there will be no possibility to filter only those tagged to a specific language. This is limiting the filters. There isn't only one usecase for that filter
Option 2 would allow anyone to filter exactly what he wants withou doing some magic behind the scenes. It is much more intuitive.
I agree with Bakual. For small pages version 1 seems to be more intuitive. However, if you have a very large page with a lot of content, version 1 is rather confusing. I think version 2 is the better alternative if the technical basis is reliable.
Solution 2 is my Choice as its also similiar to other Solutions in Joomla.
Solution 2 seems more intuitive to me.
I understand the batch example and that makes sense I had not considered that use case.
Thhanks for all the feedback I shall look at implementing option 2
| Status | Discussion | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-03-24 09:51:16 |
| Closed_By | ⇒ | brianteeman |
Proposal 1 does not look right to me as it could include a lot of items in the case of articles for example.
2 could be Ok if no unwanted behavior. (Introducing Multiselect has created a lot of issues).
But basically, I am OK with the filters as they are. If one wants to see which items are tagged to ALL, then filter such.