Filter Views queries for Entity Translation content by proper language

This sounds all good, I'm not aware of any other effort in this direction so feel free to proceed with your plan :)

Thanks!

I suppose you show this #1330332: Entity translation: Views field language filter after you started this issue
this proposal seems all good
I would be willing to test the patch if time permits

thanks

"Views" was added back into the title because that is what the issue summary is about. If you are choosing to do a more generic solution that extends beyond views, it would be good to update the summary with the current focus of the issue.

Thanks!
Kristen

I created an alternate approach, #1524210: Expose entity translation table to views, that exposes the entity translation table and adds a relationship to each entity table. The main idea was to expose the actual table so you could create a UI for translators, but you can also filter out content that has a particular translation.

The approach described above would be more of an automatic approach though, so maybe they can co-exist.

Any progress on this?

I discussed this with danielnolde some time back, and we concluded that this is no longer necessary with the more extensive views integration already commited.

@fabsor or anyone else aware of this issue:
#9 suggests that "this is no longer necessary with the more extensive views integration".
May I ask what specific views integration takes care of this issue?
I have all latest dev versions installed, but still can't filter in views by entity translation language.
If you have any guidelines, please share. Thanks

You can add a relationship to the entity translation table, and from there you can add entity translation: language as your filter. This filters out entities on a specific language.

@fabsor that is an amazing snippet of information that has solved the problem I was having.

One other thing... this might be cause for a new issue.. but what about Views for search (Search API with solr backend I'm using)? Just checked and only 'indexed node' things seem to be available for use in relationships, thereby back to the same problem as before..

i'm using the search_api_et module as well.

Any news on this? I am trying to show a view of indexed nodes through Search API with a translated body field. The Relationship is indeed missing here, and when I use the usual language filter my view is empty.

i'll go ahead and re-open this one as well.. as per #11 above:

relationship: Content: Entity translation: translations
filter: (Translations) Entity translation: Language (= Danish)
field language: Current user's language (which would be english while running Views preview; but guessing overridden by filter??)

what i set for filter language has no impact on language of output (it is always English version).

without filter (the path for this page view is set to json/data):
en/json/data -> gives English data
da/json/data -> gives Danish data

Same problem as #17

I needed to ensure that only nodes in A) the current language and B) published translations show up in a view. Here is how I fixed it from a custom module:

/**
 * Implements hook_views_query_alter().
 */
function MYMODULE_views_query_alter(&$view, &$query) {
  if ($view->name == 'MY_VIEW_ID') {

    $join = new views_join();
    $join->table = 'entity_translation';
    $join->field = 'entity_id';
    $join->left_table = 'node';
    $join->left_field = 'nid';
    $join->type = 'inner';
    $query->add_relationship('entity_translation', $join, 'node');

    global $language;

    $query->where[1]['conditions'] = [
      [
        'field' => 'entity_translation.language',
        'value' => $language->language,
        'opperator' => '=',
      ],
      [
        'field' => 'entity_translation.status',
        'value' => 1,
        'opperator' => '=',
      ],
    ];
  }

  $query->distinct = TRUE;
}