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.
Node language is a feature of node module and locale module, and works without content translation module turned on. Although Views says the node language is a node translation filter. It should be available even if content translation is turned off. One can have a blog and post different language posts without ever translating them, so node languages work without content translation being turned on.
Comment | File | Size | Author |
---|---|---|---|
#20 | views.locale-language.20.patch | 4.07 KB | sun |
#13 | oy_vey1.jpg | 51.92 KB | iamjon |
#10 | views-node_language_0.patch | 8.25 KB | dawehner |
#8 | views-node_language.patch | 8.44 KB | dawehner |
#4 | views-node_language.patch | 9.15 KB | dawehner |
Comments
Comment #1
Gábor HojtsyErm, of course not only filter, but also field, sort criteria, etc. Retitled.
Comment #2
nedjoYes. We should move that field and its accompanying handlers from the translation (back) to the node module.
Comment #3
merlinofchaos CreditAttribution: merlinofchaos commentedHm. This never happened. It still should
Comment #4
dawehnerHere is a patch.
Comment #5
merlinofchaos CreditAttribution: merlinofchaos commentedHmm:
Comment #6
dawehnerUpdate status
Comment #7
merlinofchaos CreditAttribution: merlinofchaos commentedSetting needs work since I couldn't get the patch to apply.
Comment #8
dawehnerAnother try
Comment #9
merlinofchaos CreditAttribution: merlinofchaos commentedAck. My commit spree has made this not apply *again*. :/
Comment #10
dawehnerUpdate
Comment #11
esmerel CreditAttribution: esmerel commentedbumping up in the needs review list
Comment #12
dawehnerIt's ok when you do it :)
Comment #13
iamjon CreditAttribution: iamjon commentedOk this is what I did.
I patched views 6.x2.11 and installed it on a vanila d.6.
I installed locale.
I gave page the option of multi-language with translation in submission settings.
I had one node in english and I devel generated 25 nodes, without language. I tried filtering and adding node translation arguments, and got broken handler language does not exist.
I did not find any option to sort the posts by language.
Comment #14
klonos...shouldn't this go against latest dev? Also, I need to ask: would 7.x and 6.x-3.x benefit from this too?
Comment #15
BenK CreditAttribution: BenK commentedSubscribing
Comment #16
Gábor Hojtsy7.x would especially benefit from this since 7.x sites could very well use language support without the code translation module enabled. The contrib entity_translation module provides translation UI on the field level, and people are building sites with only that, and no core translation module. The node level language information is still used in that case heavily.
Comment #17
mariomaric CreditAttribution: mariomaric commentedAny news on (7.x version) of provided patch?
Comment #18
Kristen PolFor entity-translated nodes, you can use the "Field Language" option in the "Advanced - Other" section that is provided by views.
But, I think it still seems useful to be able to have a view based on the "Content Language" filter even if no translation is happening on the site.
Comment #19
steinmb CreditAttribution: steinmb commentedWould love to see a port of the original D6 patch make it's way into 7. Is anyone working on porting the patch in #10?
Comment #20
sunAttached patch moves the node.language field and filter definition from Translation module to Locale module support.
Comment #21
damiankloip CreditAttribution: damiankloip commentedThis looks good and makes alot more sense to live in locale.
Comment #22
dawehnerJust changed the patch to use hook_views_data_alter instead of hook_views_data for node.language.
Thanks for the help on this issue!