Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Updated: Comment #N
Problem/Motivation
Once we have #2161853: Add views language filter fallback, if node not in language of filter: show in source, show in X, hide in place, content lists provided by language-filtered views will be able to (optionally) include content in a default/defined language (most likely the source language of each content piece) as a fallback mechanism if that content happens to not be translated yet to the current page language.
It would be really great UX-wise to provide links so that users with the right permissions can jump straight to translating these pieces of content to the specific language.
Steps to test.
- Enable core module Content Translation
- Edit content type Article and enable under Language Settings the option 'show language selector on create and edit pages' and enable the option 'Enable translation'
- Make sure the body and title fields are translatable..
- Go to admin/config/regional/language and add a new Language ie Dutch.
- Create a new Article and save as language English
- Create a new Article and save as language ie Dutch
- Edit frontpage view and add new filter, filter by language and select 'Current user language' and ' default site language'
- Edit frontpage view and add new filter, filter by language and select 'Current user language' and ' default site language'
- Go to the frontpage view and set the site language to Dutch. You'll see two nodes; the untranslated English and the translated dutch.
Proposed resolution
Add a link to the context to translate the entity to the page language.
Remaining tasks
User interface changes
API changes
Original report by @username
Once we have #2161853: Add views language filter fallback, if node not in language of filter: show in source, show in X, hide in place, content lists provided by language-filtered views will be able to (optionally) include content in a default/defined language (most likely the source language of each content piece) as a fallback mechanism if that content happens to not be translated yet to the current page language. It would be really great UX-wise to provide links so that users with the right permissions can jump straight to translating these pieces of content to the specific language.
Example use case scenario:
- Site has 2 languages enabled for its content (lets say English and Italian).
- The front page is as view of content set to filter the list to the current language with a fallback to the source if a piece of content is not translated yet.
- A user with the translator role comes to the front page and switches the language to Italian.
- What they see is a list of content shown in Italian if the content is already translated to that language + some content in English (not translated yet - shown because of the fallback).
- Next to each content shown in English there's a "Translate to Italian" link. When the translator hits the link, they are taken to the edit form for the Italian.
- Once done translating, they hit the save button and they return to the view where they started from, only this time the content they just translated in shown in Italian.
- They move on to translate the next piece of untranslated content.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | translatetocurrentlanguage.png | 5.81 KB | rbosscher |
Comments
Comment #1
clemens.tolboomComment #2
rbosscher CreditAttribution: rbosscher commentedComment #3
clemens.tolboomComment #4
jhodgdonSo this should be postponed on #2161853: Add views language filter fallback, if node not in language of filter: show in source, show in X, hide right?
Comment #5
jhodgdonwhoops, don't really need two-way relationship. :)