On the project page: Use the same branch of the Views version you are using (2.x. 3.x)
After installing the module (Version 6.x-2.0), it says (under admin/build/modules): Translation of views strings and content selection for views. Requires Views 3.x

Doesn't Internationalization Views 6.x-2.0 work with Views 6.x-2.x (Views 2)
and 6.x-3.x with 6.x-3.x (Views 3) or am I misunderstanding?

Comments

Jax’s picture

I have the same question.

Stephen Scholtz’s picture

Ditto.

I've got Internationalization Views 2.0 and Views 2.8 installed, and none of the fields in my views (in my case, taxonomy terms) seem to be translated.

LarsKramer’s picture

Yes, I was confused too by that phrase. Maybe the module.info for ver. 6.x-2.0 just needs updating?

In any case, the module seems to work fine for me.

@Stephen: You need to go to "Translate Interface" and "Refresh Strings". Your strings won't show up before you do that (well, they do, but as "built-in interface").
Also try installing latest version of Views: 2.11.

When I refreshed strings, I got this message:

The string backlinks:default:empty for textgroup views is not allowed for translation because of its input format.
The string image_gallery:default:empty for textgroup views is not allowed for translation because of its input format.
The string admin_content:default:empty for textgroup views is not allowed for translation because of its input format.
The string top_content:page_1:header for textgroup views is not allowed for translation because of its input format.
The string top_content:page_2:header for textgroup views is not allowed for translation because of its input format.

Gabriel R.’s picture

This is confusing, indeed. Subscribing.

benklocek’s picture

Subscribe

dawehner’s picture

It should link directly to the comment with the patch.

I guess https://drupal.org/node/357529#comment-1301226 is the right for views2

bojanz’s picture

I suggest discouraging people from trying to use the patch for views 2.
Views 3 now has the support for this module built in. Views 2 has a patch that is almost two years old. It's obvious which approach is saner.

And in any case, there are fewer and fewer reasons to use Views 2 at all, especially with another Views 3 prerelase approaching.

bojanz’s picture

I suggest discouraging people from trying to use the patch for views 2.
Views 3 now has the support for this module built in. Views 2 has a patch that is almost two years old. It's obvious which approach is saner.

And in any case, there are fewer and fewer reasons to use Views 2 at all, especially with another Views 3 prerelase approaching.

dawehner’s picture

In general the views2 patch should be well tested in openatrium.

miro_dietiker’s picture

Status: Active » Fixed

In 2.x it is clearly written that it needs views-2.x and not 3.x now.

Status: Fixed » Closed (fixed)

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