Hi,

This module is interesting, but it doesn't use terms translations in breadcrumb building, so it is annoying.

Do you plan to add translated terms support ?

Thank you.

Comments

MGN’s picture

I'll have to look into this more to make sure I understand whats involved. In general, if you, or someone else who is interested, can contribute a patch, I would be happy to review it and get it in to the -dev version for testing.

Thanks

MGN’s picture

StatusFileSize
new1.37 KB

O.K. I tracked down a similar post you made to FAQ module: #300959: Does Faq support i18n Translated Terms ? and just mimicked the solution there. Here a a patch against the 6.x-1.0 version. Can you try it out and see if this does what you need? If it works for you, I'll commit it to the 6.x-1.x-dev version and it will eventually be released into the next stable version.

chipway’s picture

Yes !

i tested it and it does the right translations.

Thank you very much.

MGN’s picture

Assigned: Unassigned » MGN
Status: Active » Fixed

Great. This has been commited to the 6.x-1.x-dev version.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ermannob’s picture

Sorry guys, but I can't get it to work... I have a vocabulary with localized terms. Terms have translations but in breacrumbs they appear only in the base language.
I'm using the dev version... any hint?

Thank you.

ermannob’s picture

I found the solution: http://drupal.org/node/300959#comment-1506732
Sorry for bugging around... :-)

ckidow’s picture

Yes same here... if "localized terms" is set, breadcrumbs will be rendered in default language in my case.

Anonymous’s picture

Version: 6.x-1.0 » 6.x-1.1
Status: Closed (fixed) » Active

I think I should add my request in this thread, as it is very related.

I've gotten to show translated terms in my breadcrumbs, thumbs up!

However, I'd also like to alter the link for the breadcrumb depending on the location. As of now, that is not possible.

let's say I have a term 'Diensten' (my default language is Dutch), translated as 'services'. I've set the breadcrumb to link to content/diensten

Now, when I go to an english page assigned the term 'Diensten', I neatly get the following breadcrumb: "Home › Services › -english test-"
However, the 'Services' Crumb now links to en/content/diensten (which does not exist). I've tried to fix this with URL-redirects, but due to content/diensten already being an url alias disallows this (temporary) fix.

So, the request is: can you make the breadcrumb path localizable?

Anonymous’s picture

Status: Active » Needs review
StatusFileSize
new1.39 KB
new1.22 KB

I've been working on this myself, as I really loved to see this feature. Editing the term URL on the english page will edit the english URL used, editing on the dutch page 'Edit term' will edit the URL to be used in the dutch breadcrumb etc.

i'm all new to the patching and stuff, so I'm sorry if I did it incorrectly.

organicwire’s picture

StatusFileSize
new682 bytes

What's still a problem is the translation of the Home link. It's simply not translated to another language than english.

What I did
- I installed the module
- Under Site configuration > Taxonomy Breadcrumbs I deleted the text in the field Home breadcrumb text
- Later, I put the word Home into the same field

When switching to another language than english, Home is not translated.

The attached patch should fix that.

MGN’s picture

Sorry, but the patch in #11 needs work because its not a valid use of the t() function - its intended for static strings only. Search around d.o. and you'll find this has been explained before.

Has anyone had a chance to test the patches in #10?

Anonymous’s picture

After being out of the drupal works for a while I was surprised no one really tested my patch. I hope someone else gets to testing it, so it may even be incorporated in a newer version?

gisle’s picture

Issue summary: View changes
Status: Needs review » Closed (outdated)

The Drupal 6 version is no longer supported. Closing this as outdated. If you think this is still relevant for Drupal 7 or Drupal 9, please open a new issue.