Doesn't work when vocabulary Translation mode is set to "Localize terms"

I had the same experience, except that I am not (yet) using CCK on this site so that's not the issue.

However, I did some playing around with the settings to test it. When creating/editing a vocabulary I have four options for the "Translation mode" (under "Multilingual options"). If I choose "None", "Per language terms" or "Set language to vocabulary" then TSS works fine. However, if I choose "Localize terms" then it doesn't work at all. No error messages, just that when I create/edit content I get the old list, not the check-boxes I want. Unfortunately, Localize terms is the only setting that makes sense for this site...

I'm using Drupal 6.9 with TSS-6.x-1.0. I'm also using a bunch of other modules. I'm not going to list them all here, but they're all the latest "recommended" version for 6.x - nothing from CVS and nothing hacked or patched. SInce it seems to be some sort of conflict with the multilingual stuff, the modules I'm using in that area are:
- Active Translation 6.x-1.2
- Internationalization 6.x-1.0
- Consistent Language Interface 6.x-1.6
- String Overrides 6.x-1.7 (but haven't set any yet)
- Swedish stemmer 6.x-1.0
- Translation Overview 6.x-2.0
- Translation status 6.x-1.0
- Translation table 6.x-1.0-beta1
- Transliteration 6.x-2.0

I have declared a few of the site variables to be multilingual - bog standard as per the handbook, the relevant bit of settings.php (and the only changes I made to that file) reads:

$conf['i18n_variables'] = array(
  'site_name',
  'site_slogan',
  'site_mission',
  'site_footer',
  'anonymous',
  'menu_primary_menu',
  'menu_secondary_menu',
);

I can't be certain this is the same issue the original poster had but it's the same symptoms (TSS just doesn't kick in on D6). Maybe they can respond and say what their multilingual settings are.

I'm changing this to a bug report since I think it's a bug :)

Confirming the same issue as slarti

I'll be glad to sponsor a fix if it will help speed a resolution.

Thanks
Alan

there is a very easy fix for this problem

set the weight value of the module taxonomy super select to 11 or higher.
Than its called after i18ntaxonomy and it works :)

Thank you dereine! Your solution is simply and working!

perhaps this could be integrated into the install file

Changing the module weight worked for me too, thanks!

Hi. Sorry, I know this is quite an old issue, but could some one please outline the steps I would need to take in order to change the weight of a module, since I'm having the same problem with localized terms and TSS.

Thanks

I found that this can be achieved simply in drupal 6, without accessing the database, using the utility module - http://drupal.org/project/util. However I now have a problem in that the translations I set up with localized terms are no longer taken into account when viewing my vocabularies when creating content for example...

I've been trying to get this to work for a few weeks now, but no matter what I try the problem persists. I really like the TSS module and I'd love it to work with localized terms on my site. I know the problem could be any number of things and that its difficult to say exactly but could any one offer any advice on a solution, given that even with changing the weights of the modules it seems to be one functionality or the other and not both?

Thanks in advance.

use this patch changes weight of module on install
run patch from the module's directory

Thanks for your response GiorgosK,

I've tried running your patch at the command line (Mac osx) but I'm receiving errors. I moved the patch into my taxonomy super select directory and, from that directory ran the patch command. At first my mac was reading your file as .patch.txt so I changed it to just .patch in emacs (and also removed the leading numbers from the name), thinking that was the problem, but the error persisted.

I used this command (on the .patch file):

patch -b < tss_weight_adjustment_to_work_with_i18n.patch

and got this response (which is the same as I got for the .patch.txt file):

(Stripping trailing CRs from patch.)
patching file taxonomy_super_select.install
Hunk #1 FAILED at 14.
1 out of 1 hunk FAILED -- saving rejects to file taxonomy_super_select.install.rej

The contents of your .patch file for reference:

--- taxonomy_super_select.install.orig Sat Nov 07 13:56:38 2009
+++ taxonomy_super_select.install Sat Nov 07 13:56:48 2009
@@ -14,7 +14,7 @@
// This module must run after the main taxonomy module,
// as it alters that form in turn.
$taxonomy_weight = db_result(db_query("SELECT weight FROM {system} WHERE name='taxonomy'"));
- db_query("UPDATE {system} SET weight=%d WHERE name='taxonomy_super_select'", 1 + $taxonomy_weight );
+ db_query("UPDATE {system} SET weight=%d WHERE name='taxonomy_super_select'", 10 + $taxonomy_weight );
}

/**

I'd be really appreciative of any suggestions you have at this point.

@anasynth
I suspect this is due to the fact that the patch was made into a window system and the line endings might be different
but anyway,

this is a trivial patch and very easy to apply by hand
go into the "taxonomy_super_select.install" and 3 lines after line 14 change the 1 to 10
this is exactly what the patch says, learn how to read a patch it will come in very handy (read more on link above)

NOTE:
if you have previously installed the module maybe the install file won't run its code and you have to go into your "system" table in the database and manually change the "weight" from 1 to 10 (util module didn't work for you ?)

Thanks for the link GiorgosK, I'll check it out for future reference.

Util is doing its job fine, it just isn't producing the effect I would like. I've tried changing the weight (to 11 I think it was supposed to be by the way) now both ways, with util and manually in the .install file (following your instructions). This is the situation:

- Before I started changing the weights (so by default i18n was called before TSS), my Taxonomy Super Select settings would not work with vocabularies that were set to Localized terms. The translations of the terms worked fine but the TSS drop down form would not be displayed instead of the regular taxonomy fields.

- When I change the weight of TSS to be larger than i18n (so that TSS gets called before the term translations, as suggested above) the TSS drop down kicks in BUT the translations no longer work.

There's some other modules in the Multilingual group of my module page but all of their weights are lower than 11 so that shouldn't be an issue. It seems like for me its either one module's functionality or the other, but not both :S. If other's are having the same weirdness I would encourage them to share their experience here to see if we can spot some thing in common between our cases.

Any thoughts on how to get i18n and TSS to walk together to produce TSS style drop down menus in the vocabularies section of a node edit form that display localized terms depending on the current language setting?

This patch adjust the module weight in the install file, plus adds i18ntaxonomy integration that allows you to translate the vocabulary name, vocabulary description, vocabulary help, and term names.

hi,

I've applied the patch successfully but still I can only see the dropdown menu instead of the usual checkboxes coming with Taxonomy Super Select module.

Any tip ?

Try reinstalling the module after applying the patch.

I've solved without the patch. I've installed utils module and changed the module weights from there. thanks

dboulet, can you reroll the patch #16 to take into account the new changes? Moreover, in the 'fieldset' section, $term is not always vocabulary (for hierarchical vocabulary).

Thanks jcisio for all the work you've put into the module! I will get back to you soon with a new patch.

New patch for review. I've added an update function to increase the weight of the module.

      if ($is_vocabulary && !empty($term->help)) {
        $help = $localize ? tt("taxonomy:vocabulary:$vid:help", $term->help) : $term->help;
        $help = '<div class="taxonomy-super-select-help">'. $help .'</div>';
      }

Here I am assuming that only vocabularies, and not terms themselves, contain help text... is this correct?

I don't use i18ntaxonomy module so I can't review it right now. Hope someone does it!

I don't update the weight in the schema update, as it will be useless if i18n is installed after that. I'll fix that problem separately.

Thanks jcisio, the update function is needed for those of us who use the i18ntaxonomy module, and are updating from an older version of TSS—it keeps us from needing to reinstall the module.

You don't have to reinstall it, just disable and reenable the module. But ok, I added the update function, and a hook_enable() too, add there are people who don't read README :) That part has been committed http://drupal.org/cvs?commit=433106.

Then all that is left is the translation of help, name and description texts.

This patch needs to be committed before #936298: Both help text and description output in help text area below vocabularies to avoid a reroll. I reviewed, though not tested, and then committed it.