I have a site with 2 languages (Arabic & Hebrew). There are forum topics of both languages. In Admin > Settings > Localizer, Multilingual content display options, I checked the checkboxes for both languages, for both Authenticated and Anonymous users. Both users have privileges to access Localizer.
When I go to a forum that contains topics of both languages, the system displays all topics for an authenticated user, as expected, regardless of the current selected language (set from the Locale switch block). For an anonymous user, the system displays only those topics that have the current language locale.
If I enable the Multilingual content block, and I check the checkboxes of both languages, then the system displays all topics also for an anonymous user.
If I then disable the Multilingual content block, and delete all browser's cookies, the problem occurs again.
I'd be happy to provide more information and assistant.
Thanks,
Amit
Comments
Comment #1
Roberto Gerola commented> Version: 4.7.x-2.4
Are you using version 2.4 ?
Please, update to version 2.6.
I've just tested this feature and seems to work correctly for me.
Let me know.
Roberto
Comment #2
amitr-1 commentedHi Roberto,
Thanks for your very fast response. I upgraded to version 2.6 and it indeed solved the problem. However, when I tried to applied the 2.6 patch for the block module the patching failed. I'll look at it more thoroughly later and see if I can find a reason - perhaps somehting is broken on my side.
Another problem is that code in localizeruser seems to be using a wrong name for a column in the localizeruser table. In the db I see that the column name is nodeslocale - no 's' at the end.
I seem not to recieve this error when the localizeruser module is disabled. If I won't find something wrong here I'll open a new issue for it.
Many thanks,
Amit
This is the error message I'm recieving:
Comment #3
Roberto Gerola commentedBlock problem.
See also this post : http://drupal.org/node/111738
About the column nodeslocale.
Yes, I've renamed it in the last version to make a more coherent
naming scheme.
You should run the update procedure on your modules page.
Or call this url : http://mydrupal/update.php
Comment #4
amitr-1 commentedRoberto,
Thanks again. I still have a question regarding the block: I have drupal 4.7 and localizer 2.6. Now, should I still apply the procedure described in the post you referred me to? If I apply it, should I also apply the patch to the block module that came with localizer 2.6?
Thank you very much.
Yours,
Amit
Comment #5
Roberto Gerola commentedNo. The procedure described in the post is more recent that the version 2.6.
It is a fix for 2.6 release.
Follow the instructions of the post.
Comment #6
amitr-1 commentedRoberto,
I just wanted to tell you that now everything is working just great, and to thank you for you patience. So thank you very much for your help, and, of ocurse, for the great Localizer module.
Sincerely,
Amit
Comment #7
Roberto Gerola commentedComment #8
bianca78 commentedHere
http://drupal.cms5.si.umich.edu/node/43634
you have a link for a module
http://www.speedtech.it/drupal/switchlanguagemodule
Can you tell me if I can find this module somewhere?
I search the net for this module, but I couldn't find it.
Thanks, Bianca
Comment #9
Roberto Gerola commentedYou can download it from here :
http://wwwold.speedtech.it/drupal/switchlanguagemodule