I ran across this niche issue while setting up a multilanguage site using the latest stable Image module to manage a large gallery. It turns out image_gallery.module uses Views to display the grid of thumbnails, and the imported View (image_gallery) activates breadcrumb generation by Views based on the Taxonomy term given as an argument.

Upshot is that the taxonomy breadcrumb logic in Views 2.x (nor 3.x from what I can see) is not looking to see if i18ntaxonomy is installed and enabled for the given vocabulary. This small patch against Views 6.x-2.11 checks for the module, checks the vocabulary to see if it's using i18n, and if so applies the translation to each term in the breadcrumb. The corresponding patch I offered up on the Image module side had to perform the same trick for the node page breadcrumbs in #870654: Image node page, gallery view and subgallery view breadcrumbs not being translated.

Reviews/critiques/suggestions are welcome! I have this up and running, but am always open to a better way to do something...

CommentFileSizeAuthor
taxonomy.views_.inc-i18ntaxonomy-D6.patch894 bytesarpieb
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

Project: Views (for Drupal 7) » Internationalization Views
Version: 6.x-2.11 » 6.x-2.x-dev
Component: taxonomy data » Code
Issue tags: +internationalization

Everything related to i18n is done in the i18nviews module.

One day views3 will support translations well.

dawehner’s picture

Status: Active » Needs work
Issue tags: -internationalization

Change status

miro_dietiker’s picture

Status: Needs work » Postponed (maintainer needs more info)

Current context of fix of arguments is:
#947468: Translate Taxonomy Term Argument

Let's see if it also fixes the breadcrumb wishes...
Can you please check the other issue solves the breadcrumb also as expected?
Any input on what's missing?

heyyo’s picture

You could also use the last dev of custom breadcrumb, translation of terms is working correctly.

miro_dietiker’s picture

Status: Postponed (maintainer needs more info) » Needs work

This is an interesting overlap...

I think everything views argument translation related (including core-like breadcrumb) should be part of i18nviews.
While additional things should be in custom breadcrumb project.

This needs some coordination with the other project.

Will someone contribute this feature and provide a patch how to remove this functionality from the other project?

:-)