Active
Project:
Localizer
Version:
5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 Aug 2007 at 15:57 UTC
Updated:
12 Nov 2007 at 13:40 UTC
I have really stupid question: HOWTO translate block with Localizer module ? I searched everywhere ... (in my drupal installation, on drupal.org..) I have module "Localizer block" enabled of course... When I am adding block, there is a menu with languages, but it doesn't work - I still can't create working translation. What about simply guide? :-| THX !!!
My friend told me about "multilingual blok" but i don't see it anywhere...
Comments
Comment #1
vikingew commentedI must say I don't know/understand how this works with blocks provided by modules, but for custom blocks it works.
Comment #2
PEpe commentedI followed your steps, but there are display both blocks together - "english block" and "czech block" - and it does not matter in which language I am switched. (I created "english block", save, click "configure", select "English", save ... and the same with "czech block" - exactly your steps). Maybe bug?
Comment #3
vikingew commentedHmm strange, it works for me... I have just started to work with Localizer today so I am no expert, but maybe something else is interfearing. Which more modules do you have installed? I have 80+ modules so it shouldn't really be a problem but maybe you have something very block related which I don't have or you have it wrong somewere else.
I assume you are using latest dev release as set above, but have you also done all steps in install, like overlay files and settings.php for cache? How have you set the rest in block configuration?
Comment #4
weedoo commentedHello, I have the exact same problem. I did a web site with drupal 5.1 and there were no problems, now I changed to 5.2 for a new site I am working on, and I cannot get a block to switch from on to off depending on the current locale. If anyone has an answer, post it please!
Comment #5
edinjapan commentedThis works fine when the steps posted by yettyn are followed for Drupal 5.2 and Localizer 1.10.
By the way, when you go from Drupal 5.1 to 5.2, you have to overwrite the Localizer patches inside the sites/all/modules/localizer directory with the "new" ones for 5.2.
Comment #6
whoey commentedany estimate when 5.3 files will be ready?
or is there somewhere we can find out what needs patching to make our own 5.3 core patched?
Comment #7
Roberto Gerola commented> any estimate when 5.3 files will be ready?
In a couple of days.
Roberto