I installed views module and created some views before I installed localizer.
In localizer, I have "views global support" checked.

Does the existing views work ie produce results with contents in the language selected on the switcher, without adding a "localizer content locale" filter to the view?

How can the filter "Localizer: Activate generic support" be used?

Thanks.

Comments

Roberto Gerola’s picture

Roberto Gerola commented

If the option : Activate global views support, is active, all your views contents
will be showed in the current select language.

In fields list of your view you should be able to see also "Localizer : content locale".
There is also an option in the filters to not apply the global generic support,
but use specific filter, for example if you want show content in specific languages
regardless the current selected language.

andrict’s picture

andrict commented

my Activate global views support is active.
the view I have produces all contents without regard to the language of the contents. say an english content node which has been translated into chinese, both the english node and chinese node appear in the view unless I add a specific locale filter into the view.
Is that normal? My understanding of what you said tells me my case is not normal. Pls confirm. I would appreciate any suggestion you have if it is abnormal.

Roberto Gerola’s picture

Roberto Gerola commented

Which content type are you using in your view ?

Is active the support for this content type under localizer options ?

andrict’s picture

andrict commented

It is content type based on CCK. I confirm the localizer support for the content type is active.

This is just my wild guess. Could it be because when I install 5.x-1.7 I didn't follow the steps in 5.x-1.7 installation ie not applying the patches. The automatic support for view without locale filter didn't work either then. now I update to 5.x-1.9 following the steps of 5.x-1.9 installation. The problem continues.

The theory behind my wild guess is as follow:- Does the localizer module in 1.7 alter the database somehow relying on the patches? So if I didn't patch, that part of the backend installation was missed in 1.7. If 1.9 still assumes the existence of that part of 1.7 backend installation then in my case the localizer module does not work to the intended extent.

I would appreciate if you could confirm whether it is the case or not.

Roberto Gerola’s picture

Roberto Gerola commented

Nothing to do with db.

General views support is implemented in a way that try to guess that it is a view,
but there is no secure clue and there is no other way, that I know.
It could be related to the fact that you are using a cck content.
If it isn't a problem for you, activate a language filter on view basis.

andrict’s picture

andrict commented

OK. I understand.
Thanks. I will stick to the view language filter.

Roberto Gerola’s picture

Roberto Gerola commented
Status: Active » Closed (fixed)