When using this module with multiple language, the entities returned are in the original language. will attach in a momment a one-line patch that gets the most adequate translation for the current context.

CommentFileSizeAuthor
#2 2652710-linkit-use-translated-entity.patch544 bytesesclapes
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

esclapes created an issue. See original summary.

esclapes’s picture

esclapes CreditAttribution: esclapes as a volunteer commented
FileSize
2652710-linkit-use-translated-entity.patch544 bytes

This patch does not change the behaviour for a single language site, but improves the experience when entity translations are available.

In some cases linking to entities is a different language might not be desired, so I gues that there should be a follow up issue to enhance EntityMatcher configuration to restrict results to current language only.

esclapes’s picture

esclapes CreditAttribution: esclapes as a volunteer commented
Status: Active » Needs review

Did not update status.

anon’s picture

anon
Primary language Swedish
Location Gothenburg
CreditAttribution: anon commented
Status: Needs review » Needs work

Good idea.

I would like a test that shows how this work.

anon’s picture

anon
Primary language Swedish
Location Gothenburg
CreditAttribution: anon commented
Version: 8.x-4.x-dev » 8.x-5.x-dev
Status: Needs work » Fixed

Thanks for the patch.

  • anon committed fe36e68 on 8.x-5.x authored by esclapes 
    Issue #2652710 by esclapes: Use the translated entity when available

Status: Fixed » Closed (fixed)

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