after upgrading from RC2 to RC4 node translation filters no longer work.

when trying to add "Node translation: Language" or "Node translation: Translation set node ID" I get the error message

Error: handler for node > language doesn't exist!

Comments

murnikov’s picture

murnikov commented

same here.

marc3ls’s picture

marc3ls commented

and same here. Anyone know how to fix it? Have cleared the views cache but no luck so far. Existing views give problems when editting.

ali_b’s picture

ali_b commented

same here

renob73’s picture

renob73 commented

and here too.

murnikov’s picture

murnikov commented

Mein Gott !
I was careless enough to use the Views 2 in a production site.
Is there a bailout option of downgrading the module back to rc3 ?!
Or the database schema is not downward compatible ?

TIA
Pavel

ar-jan’s picture

ar-jan commented
Priority: Normal » Critical

Isn't this a reason to withdraw this realease until it's fixed? For me it completely breaks functionality. I replaced my database with a backup copy to go back to rc3.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Fixed

Good grief, calm down people. This is now fixed in dev.

As a work around, edit your modules/translation.views.inc file and change views_handler_filter_node_language_current to views_handler_filter_node_language on line 39.

Isn't this a reason to withdraw this realease until it's fixed?

I just released this yesterday, and contrary to the beliefs of some, I'm a human being and I do sleep.

Tivo’s picture

Tivo commented

Sorry, it does work now.

(does not work for me :()

merlinofchaos’s picture

merlinofchaos commented

Be sure to clear cache.

Tivo’s picture

Tivo commented

Thanks

murnikov’s picture

murnikov commented

Many thanks, we're back to normality (if one can actually expect it from site owners :] )
Hope you're having a good nights sleep right now.

bauhaus’s picture

bauhaus commented

Ufff,
it's OK now. You know guys, we should wait 48h before upgrading production site. Don't you think? ;)

merlinofchaos’s picture

merlinofchaos commented

When you've got a site that has real users and you will have real losses if the site goes down, always upgrade a test site first. I realize that in an ideal world I'd create releases that don't have bugs and this wouldn't be a problem, but alas, the world is not ideal, and this stuff slips through.

dave.mecha’s picture

dave.mecha commented

to get "Node translation: Translation set node ID" running, it might be useful to change the filter-handler on line 56 in translation.views.inc from views_handler_filter_node_tnid to views_handler_filter_numeric

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

leanazulyoro’s picture

leanazulyoro commented

fix in #14 doesn't work, i created an issue for that: http://drupal.org/node/336125

gabrielu’s picture

gabrielu commented
Title: node translation filters not working after upgrade to RC4 » still not working in 2.0
Version: 6.x-2.0-rc4 » 6.x-2.7
Status: Closed (fixed) » Active

It's weird, I still get "Error: handler for node > content_negotiation doesn't exist!" in Views . I checked the code, but obviously it's not this.

gabrielu’s picture

gabrielu commented
Title: still not working in 2.0 » still not working in 2.7
merlinofchaos’s picture

merlinofchaos commented
Title: still not working in 2.7 » node translation filters not working after upgrade to RC4
Status: Active » Closed (fixed)

content_negotiation sounds like something provided by an external module that you are perhaps missing. It is not the translation filter that is being discussed in this issue, in any case. You should file an issue against the module that provides the filter.

Returning issue to prior settings.

gabrielu’s picture

gabrielu commented

Yes, my wrong, It was provided by i18n. And also had an update to that module (but in the meanwhile got a better solution with Node Translation filters)