| Project: | Content Taxonomy |
| Version: | 7.x-1.x-dev |
| Component: | Taxonomy Tree |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
in D5 and 6 it was more a feature request. in D7 I sadly have to mark it as bug because it took me a week to find out that it was content taxonomies tree level limiter in the field management, which suppresses the locale and i18n support of the term field select list widget. This causes that the list is in default language only.
content taxonomy is an awesome module and thanks for the sharing! But we should put it in the info that it doesn't support it yet (suppress it)! There is no error message, and taxonomy translation is still a hussle for many. They will think it is caused by wrong translation method, and the search and try goes on and on.
Is there any line of code I can look on to contribute a patch for the next dev shot?
Best regards,
Digidog