0

I have a node type called Match. Each match have two entity reference fields that points to two nodes that has the type of Team. I built a view and use the relationship to show the matches and the information of the host team and guest team and it's fine. My problem is that the Team node is multilingual and I want to show the translation of Team fields in the view. It is obvious that the fields has a reference to the original untranslated node ID and when I use the relationship in the view it will grab that node even if it has translations.

0

You can use the Translation redirect module (part of the Internationalization module) if your users are anonymous (unauthenticated). It just issues a 301 redirect whenever translated content exists.

If your users are logged in then there is another approach I have used, use an URL alias for your nodes. Set the alias to be the same for all translated content of a node and when linking to that node use the URL alias instead of the node number.

  • I think translation redirect works on a node , I'm using a view and having a field. I didn't totally get your second solution , should I use the URL alias in the entity reference field? – Mojtaba Es Dec 13 '12 at 12:41
  • What is the value of Field Language in your view ? If it's Current language or User's language and your fields provide a translation, it should work right away. – drcelus Dec 13 '12 at 13:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.