Closed (fixed)
Project:
Frequently Asked Questions
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Aug 2008 at 06:56 UTC
Updated:
22 Apr 2009 at 15:26 UTC
Jump to comment: Most recent file
Comments
Comment #1
stella commentedIf you enable the "Multilingual taxonomy" module which comes with i18n I'm pretty sure it should work.
Cheers,
Stella
Comment #2
chipway commentedHi,
My "Multilingual taxonomy" module in enabled, and I have translated FAQ category terms, but I do not get translated terms on FAQ display.
Thank you
Comment #3
stella commentedHave you set the "Translation mode" option on your vocabulary? I use the "Localize terms" option on my test site.
Then go to admin/build/translate/search and search for the term names so you can translate them. If they don't appear, you may need to go to admin/build/translate/refresh to refresh the list of strings available. Oh, when searching be sure to remember that it is case-sensitive.
Cheers,
Stella
Comment #4
chipway commentedHi,
I did all these + Cleared cached data. I can translate FAQ terms (already done), but still no translated terms in FAQ.
??
Thank you for your help.
Comment #5
chipway commentedWhy was it fixed ??
Comment #6
skg046 commentedI've checked to be sure that what we do matches the suggestions upthread, but this is still a bug: the category labels don't render as translated, even though the strings have been entered correctly via Translate Interface. Please advise.
Comment #7
skg046 commentedComment #8
chipway commentedi confirm that i still have the issue.
Thanks
Comment #9
stella commentedSorry for the delay in fixing this. Please try the attached patch or the latest dev release (available later today).
Cheers,
Stella
Comment #10
chipway commentedFine.
It works. i got my already translated faq taxo terms as soon as i updated to your dev oct 27.
Thank you for fixing it.
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #12
stella commentedReleased in 6.x-1.8.
Comment #13
adshill commentedHelp! I still have this problem, even with 6.x-1.8 installed. For information:
I set the taxonomy for FAQ and set Localize terms and the language as English. I set the FAQ content type and made the taxonomy required.
I have found and translated the items in the translate strings page without problems.
I have cleared cache.
Then, when I go to my english FAQ question and click on "Translate", the form for the translation arrives, but without the categories selection box. If I add the question translation anyway, it also doesn't appear in the /fr/faq page.
In addition, when I go to the node/add/faq page, the categories are there (in english). If I then click on French then fr/node/add/faq doesn't show the categories.
I'm in dire need to get a translation of my FAQ online urgently but at the moment I'm not seeing anything - am I doing something stupid? Any help hugely received.
Comment #14
adshill commentedI also tried to sync the terms in the translation sync settings - also doesn't work. I'm not seeing categories in the French questions and french questions are not appearing in fr/faq. Thanks for any help.
Comment #15
stella commentedThis is unrelated to the faq module and is rather to do with taxonomy. I think you're using the wrong vocab 'translation mode'. Set the 'translation mode' to 'Per language terms. Different terms will be allowed for each language and they can be translated.' for your vocabulary.
Comment #16
adshill commentedStella thank you - I realised that the taxonomy vocabulary was in "English" and I couldn't change it. For those who may stumble on this problem - I altered the vocabulary to "Set language to vocabulary" in order to remove the language setting, and then re-saved as "Localize terms" which enabled everything to function as it should.
Very sorry for posting probably to the wrong module although if people have the same problem then I expect that they will find this thread in their search as I did! :) Thanks again.