Updated: Comment #0
Problem/Motivation
#2161845: Node views (front page, admin) do not use the proper language filter is not quite the expected behavior.
If
node 1 is in en (source), es, af
node 2 is in es (source)
node 3 is in af (source), en
And people create a view (like the front page) which is "List all the nodes in the page's current language",
the expected result is to see 3 nodes (all the nodes). Assumes fallback, see list in proposed resolution section, is show node in source language.
If the page language is en, then expected is: node 1 in en, node 2 in es, node 3 in en, is expected. (Optional expectation is that users with translation permission could see a link to translate node 2 into en. Separate issue?)
If the page language is es, then expected is: node 1 in es, node 2 in es, node 3 in af.
Proposed resolution
Add fallback to language filter, with choices of what to do when there is a result, but not a result in the language being filtered by.
Fallback choices could be:
a) show node in source language (the "language of the node", note that nodes do not have to exist in the site default. For example a site default might be en, but a node, like node 2 above could have been created in es, or node 3 created in af)
b) show node in site default language
c) show node in X language detection and negotiation method... like user account preferred language, browser language
d) hide node.
Remaining tasks
- Decide what is actually expected, or common use cases.
- Decide if this is core or contrib territory.
- After done here, might have to return to make another issue to update the default front page view.
| Task | Novice task? | Contributor instructions | Complete? |
|---|---|---|---|
| Update the issue summary | Instructions | ||
| Update the issue summary noting if allowed during the beta | Instructions |
User interface changes
No?
API changes
No?