As of commit http://drupalcode.org/project/i18nviews.git/commitdiff/959642ea26316c53b..., the content negotiation filter has been removed.

I guess this has been done during a code sprint or something, since no issue number has been attached to the commit.

How can we bring this back asap? It might help to know the reason why this handler has been removed from i18nviews ...

Comments

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented

At least it should be named differently, because it's a i18n feature.

I currently think, you can also configure the behavior with the node language = current .... or whatever... (this feature is still there, right?)
But i agree that the selection mode is a concept which we should be able to add.

Can you test if reverting the commit helps and it works after again?
Note that after renaming, you'll need to readd this filter again.

zilverdistel’s picture

zilverdistel commented

Thanks for the quick reply.

What I need for my current project is a fallback to the default language if there is no translated version of a node. I'm not able to do this with the language = one of "current, default" filter, since both nodes get listed then ...

I will test and report back.

zilverdistel’s picture

zilverdistel commented

It doesn't work, because the drupal 6 version used the function $where = i18n_db_rewrite_where($this->table_alias, 'node');, which has been removed from i18n in drupal 7.

Daniel Wehner tried to solve this using i18n_select(TRUE); and switching it off with i18n_select(FALSE); after executing the view. I'm still trying to figure out if this approach will work, but I get a "broken handler" error.

miro_dietiker’s picture

miro_dietiker
Location Switzerland
commented
Status: Active » Closed (won't fix)

In Drupal 7 this doesn't work anymore...

There's no selection mode with a fallback. i18n should first provide something like that before we can support it with views...