Once we get at least the most important parts of the Views Multilingual meta issue done (), we should update the hook_help for the Views module to make sure it explains multillingual views.
Here is the help we currently have for Views (links omitted):
The Views module provides a back end to fetch information from content, user accounts, taxonomy terms, and other entities from the database and present it to the user as a grid, HTML list, table, unformatted list, etc. The resulting displays are known generally as views.
For more information, see the online documentation for the Views module.
In order to create and modify your own views using the administration and configuration user interface, you will need to enable either the Views UI module in core or a contributed module that provides a user interface for Views. See the Views UI module help page for more information.
- Adding functionality to administrative pages
- The Views module adds functionality to some core administration pages. For example, admin/content uses Views to filter and sort content. With Views uninstalled, admin/content is more limited.
- Expanding Views functionality
- Contributed projects that support the Views module can be found in the online documentation for Views-related contributed modules.
I would propose something like this, as part of the Uses section:
Working with multilingual views
If your site has multiple languages and translated entities, each result row in a view will contain one translation of each involved entity (a view can involve multiple entities if it uses relationships). You can use a filter to restrict your view to one language: without filtering, if an entity has three translations it will add three rows to the results; if you filter by language, at most one result will appear (it could be zero if that particular entity does not have a translation matching your language filter choice). If a view uses relationships, each entity in the relationship needs to be filtered separately. You can filter a view to a fixed language choice, such as English or Spanish, or to the negotiated language of the page the view is displayed on (the language that is selected for the page by the language negotiation settings either for Content or User interface).
Independent of filtering, you can choose the display language (the language used to display the entities and their fields) via a setting on the display. Your language choices are the same as the filter language choices, with an additional choice of "Row language", which means to display each entity in the result row using the language that entity has in that particular result row. In theory, this would give you the flexibility to filter to French translations, for instance, and then display the results in Spanish. The more usual choices would be to use the same language choices for the display language and each entity filter in the view, or to use the Row language setting for the display.
Note: the UI text for "Row language" and other things mentioned here has not been finalized, and this display setting doesn't even exist yet (see), nor do language filters exist yet for all entity types (see parent meta issue). We should not add this to the help until it's actually true, and when we do, we should make sure that the help here matches the UI we ended up with.
|#7||views_help_on_multilingual_2317975.patch||3.62 KB||Martin Mayer|
|PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,572 pass(es). |
[ View ]
|#7||2015-04-18 17_37_59-Views _ D8.png||93.24 KB||Martin Mayer|
|#11||views_help_on_multilingual_second_2317975.patch||3.77 KB||Martin Mayer|
|PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 91,796 pass(es). |
[ View ]
|#11||2015-04-24 14_43_01-Views _ D8.png||140.88 KB||Martin Mayer|