Closed (fixed)
Project:
Views (for Drupal 7)
Version:
7.x-3.x-dev
Component:
node data
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Dec 2008 at 11:29 UTC
Updated:
12 Jun 2012 at 04:51 UTC
Jump to comment: Most recent file
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 commentedHm. This never happened. It still should
Comment #4
dawehnerHere is a patch.
Comment #5
merlinofchaos commentedHmm:
Comment #6
dawehnerUpdate status
Comment #7
merlinofchaos commentedSetting needs work since I couldn't get the patch to apply.
Comment #8
dawehnerAnother try
Comment #9
merlinofchaos commentedAck. My commit spree has made this not apply *again*. :/
Comment #10
dawehnerUpdate
Comment #11
esmerel commentedbumping up in the needs review list
Comment #12
dawehnerIt's ok when you do it :)
Comment #13
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 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
izkreny 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 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 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!