Posted by fibra on June 3, 2006 at 6:33pm
| Project: | Internationalization |
| Version: | master |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi,
I have tried versions of CVS from 1-Jun06 and 3-Jun-06 and both show same problem.
With a fresh clean installation of Drupal 4.7.2 and the Internationalization module, if I create a category with no language and then
add terms with no language, they are assigned the default language (in this case english).
If I edit the term and set the no language and save it, if I view it again, its back to english: it does not let me save it as not language (set language field to blank)
I set this as critical, since I cannot create language independ terms.
Could you please follow up on this issue?
Thank you very much,
Filipe
Comments
#1
I'm following up on this thread, though the issue I've met is a bit different from yours; but since I think that the cause is the same, I prefer not to open another bug report.
Here's my case:
1) Create a vocabulary with no language.
2) Inside this vocabulary, create three terms: "Development" (en), "Developpamento" (ia), "Sviluppo" (it)
3) Link these terms in a translation set
Now, if you edit one of the terms, the language information appears to be lost: it gets set to the default language of the site.
I have also some other issue (in displaying some translated node, the corresponding taxonomy term is not shown), but I'm not opening other issues since I presume it is all depending on this one.
#2
Ok, I found the cause of the problem and corrected it. Basically, there is a typo in i18n.inc, where taxonomy_get_vocabulary() is used instead of taxonomy_get_term().
Please test the attached patch to see if it solves your problem, too. In any case, it solves mine. :-)
Also, please some mantainer apply it to CVS.
#3
I got the same problem with i18n 4.7.0. After attached this patch (i18n_taxonomy_term.patch.txt) this problem seems fixed on node pages. But I found another bug on term/# pages for no language terms when visitors switch between languages.
In my site, for example, there is a no language term (id 70). It looks alright when browse to page term/70 and switch then from English to Dutch. I mean it will be expected to display the same term/70 page when switch English to Dutch. But if switch BACK from Dutch to English the display page will be NOT expected to skip from the term/70 to another term/48 page, which is an term assigned English under another vocabulary.
Is there a bug?
#4
Applied the patch in #2.
Thanks
#5