Terms should correspond to site language when using i18n
| Project: | Taxonomy context |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | won't fix |
Jump to:
I really like this menu. In its dev state it's already more useful than taxonomy_menu! I switched over from taxonomy_menu because I need nice URLs for my pages, and taxonomy_context provides them without complaint. It also works with the i18n translation module hack that allows for a multilingual menu.
I can only see two issues that need to be fixed:
1. when on any admin page, the taxonomy_context block shows all taxonomy items in all languages, rather than just the one that corresponds to the site language. For users that are not logged in, this does not happen. With the taxonomy_menu it only used to happen on the menu/block admin page itself. See attached screen2.jpg
2. the standard display of a category page displaying subcategories is really ugly. See attached screen1.jpg . Make subcategories smaller and less intrusive, maybe put them in a list.
Also, I'd really like to see the option of immediately displaying the article if a category only has one article in it and no subcategories. I hate lists of one, they make for bad usability. I'm ready to pay $50 to whoever implements this. Contact me at yutian.mei@gmail.com .
Thank you very much for your good work!
Judith
| Attachment | Size |
|---|---|
| screen2.jpg | 176.38 KB |
| screen1.jpg | 137.39 KB |

#1
Junesun,
I haven't seen the first issue you mentioned as I have not worked with multiple languages in Drupal (yet).
As for your 2nd issue, you should be able to add some styling via CSS to your style to make the subterms not so obtrusive. Addition display options for the display of sub terms are in the works. These options include:
New options are denoted in bold, the others are currently available.
Horizontal List Example
Parent Category
Parent Description.......
Child Category | Child Category | Child Category
The terminology can get confusing when working with taxonomy, vocabularies, terms, subterms, etc.
#2
(adjusting title to reflect #1. #2 is a separate issue, more like a feature or support request)
#3
(PS. I have not confirmed if this is actually a bug. I Just adjusted the title.)
#4
No one is working on the 5.x branches.
The 6.x-2.x branch supports i18n. The title look is controlled by the CSS.