Translate taxonomy term names in Views
paradiso - December 12, 2008 - 01:48
| Project: | Internationalization |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Description
I chose to translate taxonomy terms in a brand new D6 website where 4 languages are enabled.
Each term is displayed correctly in the terms-inline div (usually located just below the node title) -- as long as the website's default language is set to English.
For instance, a term will appear in French if the "fr" prefix appears in the url.
However, if I choose to display the default taxonomy/term/* list, the name of the categories (in the h1.title on top of the list) appear in English only (as they were first entered). The translations do not "pass".
#1
Sorry this behavior is not in the default taxonomy/term/* list, rather in the preset taxonomy_term View that comes with Drupal core, when activated.
#2
Marking feature request since the i18nviews module is incomplete--most things are still to add.
A potential fix is in comment #42 in [#1125854].
#3
Extending views handler (as noted in the link posted on #2) is a good option, yet here is another way to implement fields localization: through the views_pre_render hook.
The code below was added to the i18ntaxonomy.module:
/**
* Implementation of hook_views_pre_render
*/
function i18ntaxonomy_views_pre_render(&$view) {
$fields_term = i18ntaxonomy_get_fields_term();
$fields_vocabulary = i18ntaxonomy_get_fields_vocabulary();
$results = &$view->result;
foreach ($results as &$result) {
if (isset($result->term_data_tid)) {
foreach ($fields_term as $term => $ttname) {
if(isset($result->$term) && !empty($result->$term)) {
$name = str_replace('!tid', $result->term_data_tid, $ttname);
$result->$term = tt($name, $result->$term);
}
}
}
if (isset($result->term_data_vid)) {
foreach ($fields_vocabulary as $vocabulary => $ttname) {
if(isset($result->$vocabulary) && !empty($result->$vocabulary)) {
$name = str_replace('!vid', $result->term_data_vid, $ttname);
$result->$vocabulary = tt($name, $result->$vocabulary);
}
}
}
}
}
function i18ntaxonomy_get_fields_term() {
return array(
'term_data_name' => 'taxonomy:term:!tid:name',
'term_data_description' => 'taxonomy:term:!tid:description',
);
}
function i18ntaxonomy_get_fields_vocabulary() {
return array(
'vocabulary_name' => 'taxonomy:vocabulary:!vid:name',
);
}
The code it's kinda of dirty, but it's a working draft.
Make you're opinions/correction about the two methods pros and cons to see how fields translations in views should be handle.
#4
I tried the "patch" above in the version 6.x-1.0 of the i18ntaxonomy.module.
This code is not working in this context.
#5
Code block above in comment #3 seems to work for me.
You need to translate the terms before the translated terms will show up (as expected). However, the code is currently incapable of handling taxonomy terms on relationships.
#6
As a marginal improvement:
/**
* Implementation of hook_views_pre_render
*/
function i18ntaxonomy_views_pre_render(&$view) {
$fields_term = i18ntaxonomy_get_fields_term();
$fields_vocabulary = i18ntaxonomy_get_fields_vocabulary();
$relationships = i18ntaxonomy_get_relationships();
$results = &$view->result;
foreach ($results as &$result) {
foreach ($relationships as $relation) {
$tid = 'term_data_tid';
$vid = 'term_data_vid';
if ($relation != '') {
$tid = $relation .'__'. $tid;
$vid = $relation .'__'. $vid;
}
if (isset($result->$tid)) {
foreach ($fields_term as $term => $ttname) {
if ($relation != '') {
$term = $relation .'__'. $term;
}
if(isset($result->$term) && !empty($result->$term)) {
$name = str_replace('!tid', $result->$tid, $ttname);
$result->$term = tt($name, $result->$term);
}
}
}
if (isset($result->$vid)) {
foreach ($fields_vocabulary as $vocabulary => $ttname) {
if ($relation != '') {
$vocabulary = $relation .'__'. $vocabulary;
}
if(isset($result->$vocabulary) && !empty($result->$vocabulary)) {
$name = str_replace('!vid', $result->$vid, $ttname);
$result->$vocabulary = tt($name, $result->$vocabulary);
}
}
}
}
}
}
function i18ntaxonomy_get_fields_term() {
return array(
'term_data_name' => 'taxonomy:term:!tid:name',
'term_data_description' => 'taxonomy:term:!tid:description',
);
}
function i18ntaxonomy_get_fields_vocabulary() {
return array(
'vocabulary_name' => 'taxonomy:vocabulary:!vid:name',
);
}
function i18ntaxonomy_get_relationships() {
return array('');
}
The changes allow you to specify the relationships you want translated in the i18ntaxonomy_get_relationships() function. That should be automated, but I'm not sure how to automatically determine what relationships (if any) exist.
#7
Hi,
Thanks for the code.
However, I have a little request :
Do you know how to translate terms in a view, when the taxonomy field is the "All terms" ?
The code given above only works when you display one term for a node.
#8
same problem here (I think).
With the code from #6 views that are of type "Node view" translate the terms just fine. But views that are of the type "Term view" do not translate terms.
#9
Thanks mani.atico and tbannister, the code is working flawlessly for my Views + i18n install and solved a huge problem!
#10
I had the same problem, taxonomy terms in views appeared in the original language only, but tbannister's code above in #6 works just fine! This should be applied in the module's next version. Thanks!
#11
doesnt work for me, the view title is still displayed only in english using the default taxonomy_term view
What could be wrong ?
#12
I use taxonomy menu together with views.
I added the code of #6 to i18ntaxonomy.module.
The views title and breadcrumb is not translated.
The patch is "taxonomy/products/%".
I use as argument termID with depth and as title %1.
I have set a depth of 3.
I cleared the cache and also views cache.
Any ideas why this does not work?
#13
For a while I was satisfied with tbannister's improved code since I only used "Taxonony: Term". Now I also need a field "Taxonomy: All terms", and like in #7, the translations disappeared.
Has anybody found a solution by now?
#14
The following code (implemented by my general purpose ew module) builds on #3's idea of using hook_views_pre_render to ensure that the title of the default taxonomy view is passed through i18n's translation function.
<?php
function ew_views_pre_render(&$view) {
//the following translates taxonomy_term views titles, assuming they're being set by the argument handler
if($view->current_display == 'page') {
if($view->name == 'taxonomy_term') {
$tid = $view->build_info['query_args'][0];
if($tid && $term = taxonomy_get_term($tid)) {
$term->name = tt("taxonomy:term:$term->tid:name", $term->name, NULL, TRUE);
drupal_set_title($term->name);
}
}
}
}
UPDATE: before using this also see <a href="http://drupal.org/node/346028#comment-1638984" title="http://drupal.org/node/346028#comment-1638984" rel="nofollow">http://drupal.org/node/346028#comment-1638984</a> below
?>
#15
Can the code presented in this topic solve my translation problem? Please also see #12.
I have added the code of #6 to i18ntaxononomy.module but it does not work.
Does anyone have a solution?
#16
In this code:
function i18ntaxonomy_get_fields_term() {
return array(
'term_data_name' => 'taxonomy:term:!tid:name',
'term_data_description' => 'taxonomy:term:!tid:description',
);
}
I have to change some sentence??? or to add more sentences??? because don't work.
#17
I ran into this just now like jonowindsurf...I tried something like below.
<?php/**
* Implementation of hook_views_pre_render
*/
function i18ntaxonomy_views_pre_render(&$view) {
if($view->base_table == "term_data") {
$i =0;
foreach($view->result as $term) {
if($term && $term = taxonomy_get_term($term->tid)) {
$view->result[$i]->term_data_name = tt("taxonomy:term:$term->tid:name", $term->name, NULL, TRUE);
}
$i++;
}
}
}
?>
Little dirty but seems to work. In taxonomy term views the terms translated correctly. Give it a shot.
#18
I have added your code to i18ntaxonomy.module, but the terms are not translated.
How did you apply this patch? Do I need to change something else?
I use taxonomy menu together with views. Please also read my previous posts for more info.
Thank you.
#19
If you extend the build in taxonomy_term view with (for example) some filters, the code in #14 fails. This is because not only arguments will end up in
$view->build_info['query_args'], but also filters.Obtaining the tid can better be done by using
$view->args[0]in this case.<?phpfunction ew_views_pre_render(&$view) {
//the following translates taxonomy_term views titles, assuming they're being set by the argument handler
if($view->current_display == 'page') {
if($view->name == 'taxonomy_term') {
$tid = $view->args[0];
if($tid && $term = taxonomy_get_term($tid)) {
$term->name = tt("taxonomy:term:$term->tid:name", $term->name, NULL, TRUE);
drupal_set_title($term->name);
}
}
}
}
?>
#20
I have added this code to i18ntaxonomy.module.
The title is not translated.
My view settings are:
1. Arguments: Taxonomy: Term ID (with depth)
Title: %1
Validator options: Taxonomy term
Argument type: Term ID's separated by , or +
Allow multiple terms per argument is selected
Set the breadcrumb for the terms parents is selected
Filters:
1. Node published: Yes
2. Node translation language = Current user's language
3. Node type= product
4. Content: Show in <> no
Sort criteria:
1. Sticky desc
2. Content: Art. asc
Are these settings correct?
#21
I liked the solution in http://drupal.org/node/64004#comment-1125854, so I extended it to also translate the Taxonomy: All terms field. I've attached my entire custom module, in case anyone wants to try it out.
#22
The module in #21 seems to be exactly what we needed. Sure beats hacking views.. thanks dboulet!
#23
#21 = awesome. thanks so much for this.
#24
Here's a patch that adds the code from #21 to the i18ntaxonomy module, please review. Thanks again to greenSkin for getting this started.
#25
I have tried the module of #21.
The terms are not translated.
Do I need to change something else to other modules?
I have following module versions installed:
- Internationalization 6.x-1.x-dev (2009-May-21)
- Views 6.x-2.5
- Taxonomy Menu 6.x-2.x-dev (2009-May-31)
Thank you.
#26
Hi tomsm, try this one instead, and remember to clear your cache. I've also attached a patch to replace the last one.
#27
We are using the module from #21 and I just wanted to point out one issue we had.
It seems that in i18ntaxonomyviews_handler_field_taxonomy pre_render, the array being passed did not have a term_data_tid property. It only had a tid property. It was a quick patch, but fixed our issues.
This was causing the context to get confused and it didn't return the translations, and caused "preg_match" errors when viewing the page.
#28
I have tried the module and also the patch. I cleared the cache of views and drupal.
But the terms are still not translated.
It is the first time that I applied a patch using Eclipse for Windows.
I had to use "Guess" once for the i18ntaxonomy.module file.
#29
@tomsm, How are the terms being displayed, which fields are you using?
#30
I do not use fields, because I use the page display. (please also see the attached screenshot)
I use a modified taxonomy_term default view together with the taxonomy menu module.
Taxonomy Menu passes the arguments to this view.
Please read my previous post #20 for more information.
Thanks for your help.
#31
Same module versions as tomsm, it does not work for me either using the custom module.
#32
@tomsm, otinanism, The module/patch that I provided only translates terms names that are displayed as fields. If I understand correctly, you are wanting to translate the page title on taxonomy term pages? This is a feature that would have to be added.
#33
@tomsm, otinanism: the view title can be translated in the i18n-6.x-1.x-dev release which have an i18nviews module for this, give it a try!
#34
This is awesome! Thank you guys for the module and the patch in 27 as well. You saved me hours. Works as advertised :)
#35
Thanks for the tip. I have already i18n-6.x-1.x.dev (2009-May-21) installed.
The taxonomy term (title of the view= %1 = first argument) is not translated.
If I type a word as title, for example "Products", it is translated, but taxonomy terms as title are not.
I have installed views 3.x-dev, this does not help.
Also the breadcrumbs (= taxonomy terms) are not translated.
#36
Using 6.x-1.x-dev (2009-Jun-13) :
---------------------------------------------
1. Views Title is translated
2. Views Term is not translated
#37
using 6.x-1.1
the module from #26 with the patch from #27 works partially for me (as it did using 6.x-1.0). In the same view:
Taxonomy: All Terms Vocabulary, fields and title in table view are translated
Taxonomy: Term, as exposed filter not translated
All terms displayed in both cases belong to the same vocabulary, strangely enough they are not always translated.
#38
Since I have a very tight schedule to finish my client website order ASAP then I take over Taxonomy Block module (http://drupal.org/project/taxonomy_block). IMHO, this is the easy way because i18n and View are very2 complex module to understand!
Now, Taxonomy Block supports multi-languages! This module also support parent-child style for html-list.
Taxonomy Block 6.x version is a new re-coding. Currently only support 1 block but I will expand to support several block, support page (this is important if you have very2 long term list) and order by term weight. Hope I have more spare time for coding next week.
Try it and give your suggestion and bug reporting :)
#39
I installed the i18ntaxonomyviews module from #26 and it worked as advertised for translating taxonomy in (table) views and exposed filters. Thanks!
#40
Apparently, I was too hasty with my comment yesterday, because exposed filters based on taxonomy are not translated yet. Sorry for the confusion.
#41
toemaz: Try Taxonomy Block 6.x, (http://drupal.org/project/taxonomy_block) hope this module will solve your problem until i18n and Views work fine.
#42
the patch from #26 by dboulet seems very good!
http://drupal.org/node/346028#comment-1664274
it patches on HEAD, while from my understanding i18n currently is developed against the DRUPAL-6--1 branch.
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/i18n/?pathr...
vs
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/i18n/?pathr...
so i just ported the patch. hope this helps, for me it works, please review it. josef
#43
Same issue with 6.x-1.1 as tomsm stated in #12 and #30. The argument taxonomy id/term is not translated when put as the page title %1.
Help would be appreciated.
#44
@dasjo, Looks like you're right, thanks for the patch.
@Martin Möhwald, I'm experiencing this issue as well, I'll try working on a fix.
#45
Also "the breadcrumbs" and "the taxonomy term under each teaser" are not translated.
@dboulet: Good luck and thank you!
#46
@dboulet
thanks for your i18ntaxonomyviews module! it works pretty well for me- displaying multilingual taxonomy terms n a view.
just one thing that seems not to work- when using "taxonomy:all terms" it works fine. when using "taxonomy:term" (we
have a 1:1 relation between a node type and a vocabulary) the taxonomy term is NOT displayed. A warning results
warning: htmlspecialchars() expects parameter 1 to be string, array given in /var/www/.../bootstrap.inc on line 735.
This only happens when being in another language than the default language...
And one question for my understanding- does i18ntaxonomyviews do the same as the patch you provided for u18ntaxonomy?
#47
Also looking for a quick fix on this issue. The argument term is not translated when put as the page title %1 in views. Been working for hours trying to find a workaround.
Thanks for your help.
#48
Here's a new version of the i18ntaxonomyviews module, it should now translate term names inserted from arguments, as well as terms in exposed filters forms.
@thommyboy, try this new version of the module to see if it fixes your issue. To answer your question, yes the patches that I had submitted provided the exact same functionality as the module, but added the code to the i18ntaxonomy module instead of in a separate module. I'm not going to bother posting any more patches though, I'm pretty sure that a better solution with a different approach is being worked on at the moment.
#49
I hope that there will be a solution soon because many modules use views, such as taxonomy menu, flag, etc.
Without proper i18n support in views it is very difficult to create an advanced multilingual site.
@dboulet: #48 module does not fix my problem with taxonomy menu and flag module (default bookmarks view). Thanks for your help, anyway!
#50
Regarding #48 fix:
Term view argument titles are still not getting translated after I uploaded this. Do I need to 'turn it on' somehow or should it work immediately after I upload it?
Thanks for your help!
#51
@mrwhizkid, you might have to clear your cache for views to pick up the new handlers.
#52
@dboulet
THANKS a lot! this solved my problem- term is displayed now!
so you think in a while the view-support will be included in the i18ntaxonomy module
and i18ntaxonomyviews won't be needed any more?
greetz from germany TOM
#53
I have cleared the views cache, but still no translation of the title. I use views 6.x-3.x-dev, could this be a problem?
#54
@thommyboy
Could you tell me what version of Views and I18N you are using?
@dboulet,
I have cleared the Views cache as well as my browser cache and I am still getting the term view title showing up only in English. The terms are translated in the translate interface...
I am using Views 6.x-2.6 and I18N 6.x-1.x-dev
Thanks again for your help.
#55
I use
Views:6.x-2.6
i18n: 6.x-1.1
But i don't use the term as view-title, I just use it as a field for page/block output...
#56
@Thommyboy,
Thanks for the info.
I am using the taxonomy_term view and for some reason the title on top of every term page (after I click a term) refuses to translate into the language I am using.
I was hoping that this module would sove that problem but so far no luck...
#57
I also use a taxononmy_term view. This view has no fields so this patch/module will not work.
#58
About the module from #48:
#59
@Tomsm,
There is a workaround for this problem that I just found. It's probably not the optimal solution because it means that you will have to translate all of your taxonomy terms twice. But here it is...
http://drupal.org/node/301020
I just made the changes described there and it works. Please note though that the file is now called "views_handler_argument.inc" which is a little different than what they have there.
Hope this helps...
But I also hope that this problem can be fixed so that it will only be necessary to translate the terms ONCE.
#60
@ mrwhizkid:
Thanks a lot for the tip! The title in my taxonomy-term view is now translated.
There's is only one thing that needs to be translated: the taxonomy term link under each node teaser. Please see the attached image. I have indicated the taxonomy term link with a red circle. Do you also have this problem?
Also the breadcrumbs are not translated.
#61
@dboulet
Your new module attached to #48 works like a charm using views 6.x-2.6 and i18n 6.x-1.1. Great work! After clearing the views cache, the exposed filter is being translated. One little side note: in the exposed filter, the translated terms are not put in alphabethical order.
As indicated by others, the term title in the taxononmy_term view is not translated. I will try the solution proposed by mrwhizkid in #59.
#62
@toemaz, I could be wrong, but I think that the terms in the exposed filter form are ordered by term weight.
#63
@tomsm,
I don't use breadcrumbs so I'm not sure. It seems like you should be able to pass that through I18N using a t() in your theme template but I don't know how well that would work.
I have my view set up a little differently than yours. Since viewers can already clearly see that they are in a certain category, I chose NOT to include the taxonomy term AGAIN in the teaser so I avoided that problem altogether.
With that said, I don't see why it's not translated. I do have taxonomy terms displayed in other views around my website and I have no problem with translations.
Just to be clear, are you using the module in #48? After I activated that, the terms were translated everywhere except for the argument title.
#64
#24 worked against the latest development version of i18n
but had to include this part manually in i18ntaxonomy.module since it was failing
+ /**+ * Implemenation of hook_views_api().
+ */
+ function i18ntaxonomy_views_api() {
+ return array(
+ 'api' => '2.0',
+ 'path' => drupal_get_path('module', 'i18ntaxonomy') . '/includes',
+ );
}
#42 gives warnings and did not seem to work
#65
subscribing...
#66
Additional working implementation of #48 on 6x-2.5, used for drop down filters on an attached view.
Can't express enough thanks for this.
#67
i18ntaxonomyviews module saved my day as well. Thanks to dboulet!
#68
I'm using a term view, with a terms list grouped by vocabularies.
To me, i18ntaxonomyviews module ir working well for terms, but... vocabularies are not displayed correctly.
Are this happening to all?
Thanks!
#69
juan m, your are right.
You must edit "i18ntaxonomyviews_handler_field_taxonomy.inc" in this way:
if (isset($value->term_data_name)) {$tid = (isset($value->term_data_tid)) ? $value->term_data_tid : $value->tid;
$vid = $value->term_data_vid;
$values[$key]->term_data_name = tt('taxonomy:term:'. $tid .':name', $value->term_data_name);
$values[$key]->vocabulary_name = tt('taxonomy:vocabulary:'. $vid .':name', $value->vocabulary_name);
}
#70
Hi,
#48 works here fine so far that fields in the list contain translated taxonomy terms.
The only thing making it perfect would be that pulldowns of exposed filters would contain translated values too...
Thanks for your efforts!
Best regards
Sandro
#71
@dboulet I applyed the zip you gave in #48 and now my taxonomies are translated!!! Thank you very much for this solution. My brain was burning trying to fix this until I found this post. Thanks again.
#72
I get an operand error when I turn that module on...
latest drupal and latest views
#73
SOLUTION:
create a template file in your theme directory and simply put a t() around the output...
template should be something like views-view-field--tid-1.tpl.php and end up like this...
<?php// $Id: views-view-field.tpl.php,v 1.1 2008/05/16 22:22:32 merlinofchaos Exp $
/**
* This template is used to print a single field in a view. It is not
* actually used in default Views, as this is registered as a theme
* function which has better performance. For single overrides, the
* template is perfectly okay.
*
* Variables available:
* - $view: The view object
* - $field: The field handler object that can process the input
* - $row: The raw SQL result that can be used
* - $output: The processed output that will normally be used.
*
* When fetching output from the $row, this construct should be used:
* $data = $row->{$field->field_alias}
*
* The above will guarantee that you'll always get the correct data,
* regardless of any changes in the aliasing that might happen if
* the view is modified.
*/
?>
<?phpprint t($output);
?>
then go translate the terms in the interface... very quick and very easy.
#74
Hi, thanks for the hint, but this is not working for me inside the pulldowns of exposed filters.
could you explain me a little more how the filename has to be put together? Is tid taxonomy id?
#75
I don't think select form items can be themed in the same way.
#76
Hello guys. I use taxonomy_term view, Bulgarian and English languages enabled and Bulgarian set as default language. The module @dboulet posted at #48 provided translation strings for taxonomy menu but Views title remains untranslated. I tried everything including the t() solution but is doesn't help - instead it provides translation to Bulgarian but the title is in Bulgarian?! Thanks!
#77
@miteto, I have spanish as default language, and sometimes Drupal doesn't understand that, so I had to create some things in english (as titles, taxonomies, form labels) so then I can translate them in spanish. I'm still changing spanish terms to english to translate them.
#78
subscribe
#79
subscribe
#80
Thanks for the module in #48. It works fine when language negotiation by path prefix is enabled, but I'm currently working on a site that does not use language negotiation. Is there any way to get terms translated in views on such a site? I've tried using t() to get this done, both as suggested in #73 and as follows, but neither approach is working:
<?php// attempt one
$translated_term = t('@term', array('@term'=>$row->term_data_name), $langcode = 'es');
print $translated_term;
// attempt two
print t('@translated_term', array('@translated_term' => $output), $langcode = 'es');
?>
Both attempts just display the term name in English (and yup, I've checked to make sure that the terms are actually translated into Spanish!)
Also, just to double check, even on a site using language negotiation this module won't work to translate the vocabulary names themselves, will it (wasn't working for me but want to make sure that's not just me doing something wrong.)
#81
Though it was suggested above, taxonomy terms should never be translated using the
t()function, instead usett().Usage:
<?php$translation = tt('taxonomy:term:'. $term->tid .':name', $term->name);
?>
Also, translating term names should not be done in theme templates, but if the 18ntaxonomyviews module posted here doesn't work, then I unfortunately don't have a good alternative to recommend.
#82
Thanks for the tips, dboulet! I was able to successfully translate taxonomy term fields into Spanish in my view by using the following code in my theme template:
<?php$translated_term = tt('taxonomy:term:'. $row->term_data_tid .':name', $row->term_data_name, $langcode = 'es');
print $translated_term;
?>
This actually works without the i18ntaxonomyviews module, which works great when using language negotiation on the site but doesn't work without language negotiation since then there's no way to set the language for a particular view. Or am I missing something? Is there some other way to set the language for an entire view (not just the nodes it displays) without using sitewide language negotiation?
#83
While #48 works fine for term names it fails for translating term description. I have a view of terms where "Taxonomy: Terms" and "Taxonomy: Term descriptions" are fields. "Taxonomy: Terms" are translated, "Taxonomy: Term descriptions" aren't. Any suggestions?
Thanks for the work in this issue!
cheers, Ronald
#84
um. what about path alias?
if you have a term, say, "ethics" its alias might be example.com/blog/ethics. but in Portuguese - "ética" - the path alias won't get tanslated to example.com/blog/etica. you have to go to admin/build/path and do it very manually.
is there a way to set path aliases according to term languages? I mean, in a more streamlined fashion ;D
#85
@luco
your comment/issue is unrelated to this issue
most probably what you want can be done using http://drupal.org/project/pathauto
#86
@dboulet, I used the module from #48. worked like a charm. many thanks :D
#87
Wow, @dboulet this module works a charm! I have a question though, how can I extend this to include term descriptions? At the moment, my only solution is to do use Language Sections on the description field, but it seems like a dirty way to do it.
#88
nice module addition, congrats
#89
@dboulet: #21 module did an excellent job in translating my taxonomy terms in view... until I upgraded to views 6.x-2.7.
Now displaying a view with i18ntaxonomyviews activated results in a fatal error: Unsupported operand types in ...\sites\all\modules\views\handlers\views_handler_field.inc on line 460
see http://drupal.org/node/621782
#90
Solved - I adapted the i18taxonomyviews module from #48 so that it works for Views 2.7 now (function pre_render() in views_handler_field_term_node_tid.inc).
#91
works for me so far, thanks!
#92
The module translates taxonomy terms correctly within views, for example in filters.
But the page title, breadcrumbs and node terms are not translated on the page display of the "taxonomy term" view.
The title translation is ok by entering PHP code in de views header:
see http://drupal.org/node/301020 #5
I am still looking for a solution to translate the node terms and the breadcrumbs.
Does anyone have an idea how I can do that?
Thanks.
#93
I've tried the module in #90 and it works when using the "Term ID" as an argument, i.e. the page title changes appropriately. Thank you for this.
The next thing for me is to have the summary plugin (The option for arguments: Action to take if argument is not present: Summary) use the localized term names. Any idea on how to do this?
Marcus
#94
I tried #90 and it worked very well, thanks!
#95
#90 seems to be working for me as well, thanks!
#96
Since the i18nviews module requires i18ntaxonomy now,
can we refactor this one as a patch for i18nviews?
Btw, we are targetting now views 6.x-3.x for next i18n release. Related #360024: Write views localization plugin