Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.How can I get a complete list of nodes, including translated ones? The currently shipped view never displays translated nodes, even when I set the filters for "outdated" and "translation status" to any/both.
Is this a bug within the "Translation status" filter, or is there a filter criteria in the shipped view I need to remove, to get that filter working?
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | remove-redundant-filters-2.patch | 2.78 KB | matsbla |
| #6 | translation_view_filter_redundant.png | 66.3 KB | hudri |
| #5 | Screenshot from 2018-09-14 14-03-10.png | 85.16 KB | matsbla |
| #4 | Screenshot from 2018-09-14 14-01-26.png | 94.13 KB | matsbla |
Comments
Comment #2
hudriComment #3
hudriUPDATE:
There seem to be some issues with the "Translation outdated" field. The default view ships with 3 filter groups.
(( Filter group 1 with exposed filters ))
AND
(( Content translation: Translation status (= 0) OR
Content translation: Translation source equals row language (= True) ))
AND
(( Content translation: Translation status (= 0) OR
Content translation: Translation outdated (= True) ))
The third filter group seems to conflict with both exposed filters, "outdated" and "translation status". When I remove the third filter group, both exposed filters seem work at least when used exclusively.
The "outdated" field seems to work only for existing translations, which is kind of makes sense when applying SQL logic ("false && null" !== "false"). However I don't understand the purpose of that 3rd filter group, which seems to conflict with the exposed filters in the first filter group.
Comment #4
matsbla commentedIt is only possible to get a complete list of nodes translated into one specified target language. It is correct that the demo view filter out nodes that are translated (unless the translation is marked as outdated, then it will show up again in the list).
If you also want to see translated nodes you can need to delete the two last filter criteria in the demo view ("Content translation jobs"):
1.
However the demo view also filter out rows where source language is the same as target language, as it doesn't make much sense to say "I want to translate nodes from English to English". If you still want to see these nodes you have to do 2 or 3 things:
2.
Remove the filter:
This filter makes sure that none of the rows contain the default/original language.
3.
You also have to configure the target language filter, if you edit this filter there is an option named:
This make sure that the source and the target language is not the same for any rows, and thus you also have to remove the check for it.
Normally this should be enough to see any translated node. However when testing to give you an answer I found a bug:
#2999714: Translation source equals row language: Wrong result when target language is default language
Because of this you will still not see rows with default languages anyway.
4.
The workaround for this is to also delete these filters:
However, by doing that you will see duplication's listed for every other translation that exist of the node. So if you have a node translated into English, Spanish, and French, and you put target language to English, you will see the translation listed 3 times, first with English source language, then with Spanish and French language. A workaround for this could be to configure the "Content: Translation language (exposed)" to only allow for 1 source language to be selected. However then you would only be able to see translation status for nodes that already have a translation in the specified source language. Until the bug over is fixed there is no other workaround for this.
Edit: another solution could be to use the filter "Default translation" and make it true, then you will only see listed nodes in default language, and only see 1 instance of each translation (translated or not translated). However then you will only be able to translated from default language.
Here are screenshots of the configs I talked about:
I hope this clear things up and feel free to follow up with other questions!
Comment #5
matsbla commentedComment #6
hudriHello matsbla,
thanks for your really quick feedback. We've got a "one-way-only" translation workflow from site-default-lang to other-lang, so I think it is enough for me to use point (1) from your answer.
From a more general point of view, I still think that the 3rd filter group / the last two filter criteria from the demo view are redundant and can be safely removed from the module. Their function is fully covered by the exposed filters in the first filter group, they also prevent the exposed filters from working.
To keep the current default behavior of the demo view, the default value of the exposed filter "Translation status" can be changed to "1 (Translated)" instead.
Thanks a lot for this great module, best regards
Reinhard
Comment #7
matsbla commentedI thought about this and I agree with you, as the filters are already exposed the result becomes confusing when they also have some default hidden values.
I want to default the translation status filter to "Not translated", however I found a new small bug when trying to do that #3002659: Translation status filter is not extending boolean operator
Comment #8
matsbla commentedComment #9
matsbla commentedTrying one more time after #3002659: Translation status filter is not extending boolean operator is fixed
Comment #11
matsbla commented