To integrate the module with Entity Translation, I replaced the line 351:

->propertyCondition('language', array($language->language, LANGUAGE_NONE), 'IN')

with this:

->fieldLanguageCondition('title_field', array($language->language, LANGUAGE_NONE), 'IN')

Comments

flyke’s picture

flyke commented
Issue summary: View changes

I tried this but it doesn't work. I have a site where the original language is Dutch. I apply Flippy on newsitems, and it works great when the site language is Dutch. But when I change the language (to English) then flippy disappears. I use only Entity Translation, and tried the above but the pager does not appear. I see an empty ul with class flippy in the code.

flyke’s picture

flyke commented

Correction, above does work. I simply had only one translated newsitem. As soon as I translated another, Flippy showed up. I wrongly assumed that it would also browse through the untranslated nodes, since they show up on the website and the news index anyway. But I do find this favorable behavior, so it works as it should.

grevil’s picture

grevil commented
Status: Active » Closed (outdated)

The Drupal 7 branch will only get bug / security fixes. As of the D7 issue smashing initiative in #3309846: Check and sort out old Drupal 7 issues, I will close this issue.