Closed (fixed)
Project:
Localizer
Version:
5.x-1.9
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
18 Sep 2007 at 23:04 UTC
Updated:
12 Nov 2007 at 10:07 UTC
I don't understand how to get a view to display only content for the current locale.
Under Localizer settings,
* "Views global support" is checked.
* "Support for different contents types" has the right content type(s) chosen that I'm pulling with the view.
In the view, I have chosen "Localizer : activate generic support" ("is active" as options) in the filter.
But view shows all content for all languages no matter what locale I choose. Am I missing something?
Comments
Comment #1
patrickfgoddard commentedQuick update: While I await a more ideal solution, I'm grabbed the output from views wizard and wrapped a locale check:
Of course, this is a quick solution for one view, don't really want to do this for every view...
Comment #2
svihel commentedIm just starting with these two modules. Although I was somehow successfull to use filter you mention and it now showing only one node (not node for every translation I made), but it display wrong translation.
For example I have not yet translated all nodes, because I only trying this. All nodes is in my (czech) language and some of them are in english. When I enable localizer filter, nodes that have both translations are allways displayed only in one language. Whener I am switched in english version or czech it always shows the node in english version.
Going to continue with studying this, but for now I am kinda confused.
Comment #3
stamat commentedHi friend,
When you want to translate an article from English to Czech language , make sure that you selected the correct language and press "Change" button inside the (Home » Administer » Content management >> Edit Story XXX). Otherwise you do not translate anything. If you have succeeded , your "story" has to be duplicated in the Content List Section(/drupal/admin/content/node).
I hope that helps.
Greetings !
Comment #4
svihel commentedThanks for answer,
anyway I already figured out what is my problem. Its laziness :-p I presumed that localizer is just like any other module, so I didnt actually ready the install manual, which results in bad functionality, obviously.
For anyone who has problems with this module, and didnt read that yet, I would strongly recommend reading this guide - http://drupal.org/node/103419
Comment #5
Roberto Gerola commented