Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
hi,
the core taxonomy_autocomplete_validate simply does :
if ($possibilities = taxonomy_term_load_multiple(array(), array('name' => trim($typed_term), 'vid' => array_keys($vocabularies)))) {
$term = array_pop($possibilities);
}
so it doesn't take care of term language at all.
i'll add a patch so that we have i18ntaxonomy_taxonomy_autocomplete_validate
to take care of this.
Comment | File | Size | Author |
---|---|---|---|
#11 | i18n_taxonomy-handle_language_autocomplet_terms-2506981-10.patch | 3.39 KB | joseph.olstad |
Comments
Comment #1
izus CreditAttribution: izus commentedhere it is
Comment #3
izus CreditAttribution: izus commentedComment #5
izus CreditAttribution: izus commentedComment #6
izus CreditAttribution: izus commentedComment #7
ogggg CreditAttribution: ogggg commented#5 works for me
Comment #8
izus CreditAttribution: izus commented@ogggg can you then please set the status of the issue to "Reviewed & tested by the community", so that maintainers wil look at it
Thanks
Comment #9
ogggg CreditAttribution: ogggg commentedComment #10
Cyclodex CreditAttribution: Cyclodex as a volunteer commentedI think this patch is basically for the case of Translate. Different terms will be allowed for each language and they can be translated.
Localize has a different issue, which I am investigating now.
Comment #11
joseph.olstaddue to testbot changes the original patch needs a reroll
rerolling original patch #5
Comment #12
PieterDCMy colleague Michel tested the patch and confirms it works.
I tested it as well.
As for the code of the patch itself:
LANGUAGE_NONE
instead of'und'
.