Start with a default Drupal 7.26 installation

1. Enable (and install) the following modules:
Internationalization 7.x-1.10
String translation 7.x-1.10
Translation sets 7.x-1.10
Locale 7.26
Variable 7.x-2.4
Taxonomy translation 7.x-1.10

2. Go to admin/config/regional/language/add. Add a language of choice (for example, French)

3. Go to admin/structure/taxonomy/tags/edit. Set Translation mode to "Translate. Different terms will be allowed for each language and they can be translated." and click "Save"

4. Go to admin/structure/taxonomy/tags/fields. Add a new field from type "Image" with a random name. Click on"Save field settings". Click on "Save settings" at the bottom of the page.

5. Go to admin/structure/taxonomy/tags/add and add a Taxonomy Term with a random name. Set the language to "English". Click "Save and translate".

6. Click on "add translation" next to the extra language (in our case next to "French"). Make sure you add an image to the image field. Click on "Save".

7. As you can notice the term has not been added to the Translation Set. If you go to admin/structure/taxonomy/tags you can see that there's no language specified for the newly added Taxonomy Term. And if you click on 'edit' you can also see that it is now set to "Language neutral".

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hotbeach’s picture

I have exactly the same issue. Anybody know how to resolve that ?

webfab’s picture

Same issue here.

At step 6 if I don't clic on the ajax upload button the term is translated correctly.

Maybe related to this issue https://www.drupal.org/node/2382463, but the patch not work for me.

Regards

stijntilleman’s picture

This is still an issue with Drupal 7.41 and i18n 7.x-1.13, anyone have a solution?

Stefdewa’s picture

The problem is that the $_GET variable loses info when the page partially updates with AJAX. A possible solution is storing this info in the $form_state.

Pawlus’s picture

#4 looks promising, but gives me an error. Additional line should be modified
drupal_set_title(t('%language translation of term %title', array('%language' => locale_language_name($_GET['target']), '%title' => $source_term->name)), PASS_THROUGH);
to
drupal_set_title(t('%language translation of term %title', array('%language' => locale_language_name($target), '%title' => $source_term->name)), PASS_THROUGH);

RecursiveMeta’s picture

I am going to raise this one from the dead and do some testing. I found another issue related to this.

During an ajax request it also loses the translation set, due to the $_GET variables problem. I can do some testing and see if patch 4 is still applicable or possibly roll an update if necessary.

RecursiveMeta’s picture

I was able to apply the patch and it appears to still be working as of June 26th 2017.

#4 resolved my issue

RecursiveMeta’s picture

Status: Active » Reviewed & tested by the community
joseph.olstad’s picture

testbot barfed on filename with spaces.

Here's the same patch with some whitespace cleanup in the filename and also in the code.

joseph.olstad’s picture

Version: 7.x-1.10 » 7.x-1.18

joseph.olstad’s picture

Status: Reviewed & tested by the community » Fixed

fixed in 7.x-1.x branch
for those using 7.x-1.18 , you will need to apply the patch, or else switch to 7.x-1.x dev or wait until 7.x-1.19

postponing a release until at least a month or two.

joseph.olstad’s picture

Status: Fixed » Closed (duplicate)

reverted this commit

this issue is most likely a duplicate of :
#1787124: i18n_mode and language not respected for taxonomy_vocabulary entity

joseph.olstad’s picture

Status: Closed (duplicate) » Active

joseph.olstad’s picture

Status: Active » Needs review

Not sure if this patch is needed now that this issue seemingly related issue is fixed:
#1787124: i18n_mode and language not respected for taxonomy_vocabulary entity

Pawlus’s picture

The issue is not fixed. None of patches from the other thread work for me, icluding the one that was pushed to production. The one from note #9 is more complex, but it works.

joseph.olstad’s picture

@Pawlus, are you using entity_translation as well or are you doing content translation?
has this been tested with and without entity_translation enabled vocabularies?
or just content translation ones? string translation vocabularies? what is your vocabulary configured as?

just wondering how safe this change is.
Seems pretty safe. Just wanting to find out if reports of various configurations working for you.

joseph.olstad’s picture

Status: Needs review » Fixed

Based on feedback from @Pawlus , using patch 9

Thanks!

Status: Fixed » Closed (fixed)

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