First of all this is definitaly a great module, works like charm on content! Installation went smooth and all the modules which should be enabled according to the manual at drupal.org are enabled, even the menu localizer module. It is possible to translate content without any problems but I have no clue where the translation of the menus or the taxonomy should be possible.
There is no documentation arround to check if I'm missing something or that there is something not working. Perhaps someone can point me the way to the menu entry translation. thanks
Comments
Comment #1
Roberto Gerola commentedhttp://www.yourwebsite.com/admin/content/localizer/strings
http://www.yourwebsite.com/admin/content/localizer/content
Comment #2
pierre13 commentedI to can not change for example my own primary links.
If i search the "admin/content/localizer/content" for one of my menu items or primary links, it does not find anything.
For example one of my primary links names: "STORITVE" i then search for it and it doesn't find it in my locale and neither does it find it in another locale which we are planning to use (base locale is sl, and the other ones are ge and en).
Thanks in advance
Comment #3
pierre13 commentedForgo to set it to active. Message before.
Comment #4
tomceek commentedSearch for menu strings or taxonomies not working at all! tried different search criteria - nothing!
How to use it???
Are there possibility to translate views block, or menu, or page titles created with views module?
Example "Latest images" in English is different language there is not possible to translate using "...content/localizer/strings" or in different way...
thanks
Comment #5
GN commentedIt looks like searching a menu string usually does not work if you create a menu item as an option in the process of creating a node. The menu item is visible, but not findable (even if you run cron, reindex the site etc.). However, if then you go to menu administration and edit/save this menu item, you can find this string - and eventually it works.
Comment #6
tssk commentedI can confirm what snicers writes. I'm trying to install Localizer, but I cannot find "Translations" possibility in Menu administration. According to some manuals there should appear this possibility http://www.drupal.cz/files/localizer3.jpg after installing Localizer, but it does not.
I also don't understand Roberto Gerola's reply in this thread. Did the way how to translate Menus changed?
I found out, that in older versions some patches were needed to apply, but there is nothing in install instructions for 3.0 version. It looks to me that documentation is poor.
Thanks for any help
Tomas
Comment #7
Roberto Gerola commented>Did the way how to translate Menus changed?
Yes.
>It looks to me that documentation is poor.
Sorry, not enough time to do everything.
Comment #8
Jack_Sparrow commentedThis is very confusing...
I cannot change the menus into their foreign languages, although I somehow managed to do it for one menu item 2 days ago...
I've been trying for the past 2 days to do this, but still nothing.
What I've found is that if I view the 'page' and go to 'translations' and then 'edit' the language which I've already created, and put the menu name in the 'Menu URL settings' and hit 'submit', I see the menu now appear on every page and only then does it show up in the 'Localizer strings translation' section, but there is no way to translate it because the 'translations' link opens nothing???
Good module but the menu translation section is lacking good documentation or functionality.
How do I (step by step) translate menus, please?
Comment #9
Roberto Gerola commented> Localizer strings translation' section, but there is no way to translate it because the 'translations' link opens nothing???
It should work and show the textareas for the languages you enabled on your website where you can insert the translations.
Check also your criteria in the Search panel of that interface.
Comment #10
Jack_Sparrow commentedHi Roberto,
I've followed the online instructions re. the search section in Localizer Strings Translation section, but the searches return no results.
I've tried editing the menu on the actual page I've created and am trying to translate, but now it says that English is associated with another page and I should dissable it first. I go to that page and disable it, but the 1st page still says the same thing. Now the menu link on the 2nd page where I disabled the language goes to some other random page...???
It seems to be breaking the site apart while I'm trying to do this...
Now I have to redo every page in the site from the begginning again just because the menus don't get translated...
Like I said, somehow one of my menus were successfully translated, but how that appeard in the Localizer Strings Translation section is a mystery. Now that menu has changed and the page it was linking to has changed too.
I downloaded the latest build yesterday too.
It just doesn't seem to be working in the Localizer Strings Translation section which is obviously where the menus are to be translated. As for the taxonomies... I'm not too sure how they are translated?
Thanks for your help again. Hope our tests are assisting in getting this right?
Comment #11
Jack_Sparrow commentedTo follow up on my last post...
I've edited each page again (just resubmited the page) and checked the Localizer Strings Translation section and found the translation waiting. So I guess this works. It's just the normal menu items that I'll want to translate, like Galleries, Blogs, Polls, etc.
Comment #12
Roberto Gerola commentedThe interface strings (I mean, strings provided by modules and not inserted directly by you) should be translatable
through Drupal locale interface.
They will be translatable only if the module's developer has implemented the support for.
Comment #13
manuel garcia commentedIf i go to admin/content/localizer/strings , I cant find the titles of any menus (nor primary nor other menus).
subscribing...
UPDATE: It does seem like the trick is to resubmit the content that has the menu item after you installed localizer, this seems to make the module see it when you search in admin/content/localizer/strings
This could be quite traumatic if you have a lot of menus setup like this... thankfuly its not our case (yay!)
Cheers everyone for the info :)
Comment #14
Roberto Gerola commented>It does seem like the trick is to resubmit the content that has the menu item after you installed localizer
Yes, there was a bug in 3.0 release.
Fixed in 3.3
Comment #15
manuel garcia commentedOK, so we can translate through the string search menus that are cerated by the node form itself. However I am not finding how to translate:
As I undersetand on i18n you could specify which primary menu to use per language, is such a thing posible on localizer?
If not, how to go about translating these menu items?
I cannot find any of these using the admin/content/localizer/strings search functionality, nor on the locale search ( /admin/settings/locale/string/search ).
I have read every thread I've found on this, but I cant find a clear answer...
Thanks in advanced!
p.s. I am not changing the status of the support request, and I'm not sure wether I should open another one... so that's why i'm replying here.
Comment #16
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #17
Robert_SK commentedCould you please post brief instructions how to translate a menu item? I clicked on the links above, found the string in the menu item, translated it, but I still do not see it in the menu when
Somehow I do not understand why translating of menu items has changed in 3.X.
Comment #18
manveru commentedThe menu is working if the translated strings are present in database - I manually added them to database.