Views filter "i18n: Content negotiation" is not working properly for "Mixed current language (if available) or default lang ..."

I think if the code in Select Translation module can be incorporated here, it will fix this issue and expand usage of the views filter in terms of multilingual sites
http://drupal.org/project/select_translation

Select translation implements a Views filter which allows you to select, for a group of nodes representing a same translation, which of the translation should be displayed.

The options are :

Use current language ; if not available use original language
Use current language ; if not available use default language ; if not available use original language
Provide a list of languages, so that the most appropriate language is selected. The list can contain the special values 'current', 'default' and 'original' for, respectively, the current language, the default language and the node's original language.

Fixes the issue as advertised

Bumping version number as well

I confirm the patch is working well!

I've only modified it to work with patch -p0 < blah command (removed the C:/... stuff).

+1 the patch works. Thanks.

The patch looks good. However, how it will work with some other non views queries or whether it will work for all DBs (pgsl?) is uncertain.

As I understand, there are some other modules addressing the issue, so we won't risk regression issues at this point (Drupal 7 coming)

Hi,

We are now 2011, first reported this problem and fixed this over a year ago.
I don't see any other solution for this huge problem then applying this patch over and over with every update.

I think it's unacceptable that such a big bug is not fixed and patched in the main release :s

I think we should check the D7 version first and make sure this bug is fixed for future now.

Can someone please check and report the state of the D7 version?

...subscribing.

@Jose, #6:

...As I understand, there are some other modules addressing the issue...

Care to share which ones? Are you referring to my workaround here perhaps?

...btw I agree with the status change. This issue shouldn't simply be ignored.

This 'mixed' option has been around for a long time and never working properly.

So: we are dropping it from i18n module.

Please, consider putting together a new module for complex content selection.

WTF are you crazy ? dropping support ??? pffff

I agree. This is a serious issue for us people with multilanguage sites. It is not polite to simply ignore us. It should be decided if either Views or i18n is the proper place for it to be handled, but it does need to be handled. I do understand that figuring out a battle plan and finally coding a solid solution might be really hard, but all this "hiding the dust under the carpet" thing is not the way to go.

Perhaps we can agree on setting this to "postponed" then? Once we decide if this belongs to either i18n, Views, or some other contrib module, we can move this issue to the proper queue, but please do not close it.

Ok, "postponed", then.

Anyway, just to make it clear, if we want a stable i18n release, incomplete features that break other modules' queries cannot be there. I think adding this never fully working query rewriting was a mistake in the first place, and so far has consumed a huge amount of time from everybody.

Moreover, there's no reason why this needs to be integrated into i18n. Any other simple module could do it even easier as it doesn't need to handle different 'selection' options. Just disable i18n_select, enable the other module. Also "Select Translation" or "i18n views" would be much better candidates for this feature.

Note D7 i18n_select has an option for not rewriting views queries at all, that is enabled by default (skip tags 'views'). Maybe that should be hardcoded.

Come on, there's a tested-and-confirmed patch already! Have you even tried it?

Subscribing

This was a 6.x issue so changing version.

About this feature, it has many other problems including serious performance issues.

The patch includes subqueries and it is complex and runs for all views and non views queries. Also it would fit better as a views filter or on other modules (i18nviews, select_translation).

For the 6.x version our #1 priority is not breaking exsiting sites. About patching don't worry that much because there won't be many more 6.x releases.

So just "it fixes my views issue" is not enough here. There are many other hundreds of different node listings provided by other modules.

Please see #1252494: Create a new module for complex query altering (mixed mode) language selection.