Multilingual filtering

[crystalenka]

@angieradtke pointed out this issue when we were discussing #5 and #8. Thank you Angie!

Problem we're trying to solve:

When filtering by language in a list view, or when selecting a language in an edit view, the category filter/select still lists categories that are not available in that language. Categories not in that language should be disabled or preferably hidden, since multilingual sites are likely to have many categories and it's obnoxious to have to scroll through so many that don't apply.

(Side note: Should other filters update based on available options, too? Grey out/disable choices that don't have any results?)

Possible solutions include:

• Update the category list via AJAX when a language is selected to only show relevant categories.

Things to remember as we discuss this issue:

• This pattern is likely to be repeated in many places throughout the CMS. We should find out where else and ensure it gets updated everywhere at the same time.
• Q: Does this apply to other filters or fields, too?
• We will need to update documentation about the language select to reflect our recommendations.

[zero-24]

To me it sounds like what you are looking for is an condintional hiding or showing of fields and information similiar to the showon feature of field where you can hide complte fields based on the selection of another field.

Example: proxy enabend -> show proxy settings; proxy disabled -> hide proxy settings.

I'm not sure on a quick look how this is implemented but i guess in the end we need to trigger it in a similiar fashion and run some PHP method from within the field to execute the intended reduction of inputs, kind of a refresh with a new selection.

We should still have to keep in mind the power users who is selecting a language creates the article anyway and changes the categorie later and that limiting the options as well as too much information can both frustrate and confuse people.

My suggstion would be to get someone to write a poc form field class so we can see how such an advanced select could work and after that come back here to discuss where it should be used and that we have to keep the power users in mind too maybe with an global and or user dependet opt-out of such behavior?

[brianteeman]

Can you use the same techniques I used in the column select? That should answer your concerns @zero-24