Posted by mvc on May 26, 2009 at 12:05am
Jump to:
| Project: | Primary Term |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | sethcohn |
| Status: | closed (fixed) |
Issue Summary
I'm using primary_term on a multilingual site. I noticed that the list of terms in the form select added by primary_term weren't translated, because primary_term installs itself with weight 9, and so it runs before i18ntaxonomy (weight 10). I changed the weight to 11 and everything worked perfectly. So, I propose patching the .install file.
This also needs a call to hook_update_N() for people who already have the module installed, but I don't have time to write that now. In the meantime, in case anyone reading this has the same problem, the following query is needed:
update system set weight = 11 where name = 'primary_term' limit 1;
| Attachment | Size |
|---|---|
| primary_term_weight.patch | 668 bytes |
Comments
#1
+1 to this
#2
Needs the update function. Also, probably better to detect the current weight of i18ntaxonomy and set to one more than that, defaulting to 11 if i18ntaxonomy is not enabled.
#3
agreed. I'll be merging this with some other similar needs, to ensure it runs after all of the other items it needs to run after...
Actually, that is still a temp fix... the problem is the way it generates the list of primary terms: it grabs them from the existing form... I think we need a better answer here anyway...
I'll be releasing some primary_term code next week. Going on a small vacation first.
#4
PT now uses i18ntaxonomy to localize the vocabulary terms as it builds it's widget. Fixed in http://drupal.org/cvs?commit=438132 .
#5
Automatically closed -- issue fixed for 2 weeks with no activity.