i18n issue: field "content: title" linked to node doesn't respect current language while building URL

Feel free to hang out in the issue queue and answer all the questions.

In general i'm really not sure whether your behavior is the expected one, or how views could do something here.
Field translation is a contrib module, so views will not automatically integrate with that one.

What views does is to check out the language of the content, which sort of refers to the language defined by the translation module, not entity_translation. Maybe we would have to figure out how url() fixes this particular problem but in general it seems to be a doable question.

i am not sure if this is related; but similar much more basic issue:

- for a node type which is NOT enabled for multilingual support.
- add a "content: title" field in views
- select "Link this field to the original piece of content"

the url for this becomes /en/[title]

when the site is switched to FR, the url remains as /en/[title] when it should be /fr/[title]

i had expected Views did the "right thing" here so have this all over a site of ours. my solution has been to go through all views and add nid field and rewrite this as [title] output as a link and set link path to node/[nid]; this then does the right thing.

pretty sure this would need to be considered a bug and i will likely look in to fixing it as it will be quicker than changing all the views i have on this site. if this is no way related to this issue; let me know and i will open a new issue.

looking at the render_link function in views_handler_field_node.inc the language is pulled from this line:

$language = $this->get_value($values, 'language');

but this pulls the node_language; which is the language the node is defined in, which for node types which are not being translated; this is the Drupal base language (EN). this isn't correct. we should be pulling the site language here.

as a quick test i forced $language = 'fr' here and this mostly works. my url is now /fr/node/[nid] which does take me to the correct page (my language neutral node; but with the site in FR). but what i was hoping for was a url of /fr/[title]. this seems as though it would be a bug in the Global Redirect module as it should not allow me to go to node/[nid] if there is an path alias (and if i enter the url as /en/node/[nid] sure enough global redirect does the right thing and switches me to /en/[title])

so i am sure there is a bug in the Views handler here but i would bet not as simple as setting language to the site language. there likely needs to be a check if the node is actually language neutral and then set it to site language.

also, more as a question, a view has a setting for "Field Language" with options including "current user's lang" as well as "Language neutral". neither of these help this situation.

Removed some
for increase legibility

I don't think there should be any check if the node is actually language neutral or not. All this check is already a job of translation modules. As we can see in views_handler_field_node_link.inc (field "Content: Link" which as "Content: Path" works nicely) there is no code about language. So removing it from views_handler_field_node.inc would be convenient solution in my opinion.

Try this quick fix.

There's a module for this. Try using Internationalization Views

First enable module. Then, when building your view, use the field called "Entity Translation: Title", rather than "Content: Title".

(cross-posted because I am not sure where this issue lies, forgive me if this breaks a policy somewhere)
https://www.drupal.org/node/866170#comment-10352693

Hmmm,

The Link this field to its node feature does NOT work with a Multi-Lingual Drupal 6, Ubercart 2 implementation.

The URL for the targets that feature the Link this field to its node work correctly where they are available, i.e.:

• Content: Image
• Node: Title

With these, I get what I want and translation works properly:

English:
http://holisticpethelp.com/products/nose-it-k-9-ball-flex-red

Chinese:
http://holisticpethelp.com/zh/products/nose-it-k-9-ball-flex-red

But where this option is NOT available and when trying to link the BODY of the content associated with this product manually, things break down:

A) Include Node: Path, Exclude from Display checked
B) Include Node: Link, Exclude from Display checked (just for safety)
C) Customize Node: Body to reference [path] when Output this field as a link is checked

Will give you the following URL linked to the Node: Body text:

http://holisticpethelp.com/zh/zh/products/nose-it-k-9-ball-flex-red

A) Where in the core code for VIEWS is this happening?
B) Can anyone suggest a fix?

UPDATE! HERE'S A WORKAROUND:

Add Node ID to selected fields
1) Add Node: Nid to selected fields
2) Re-position Node: Nid to top of fields

Configure and link desired display information (in my case Node: Body)
3) Check "Output this field as a link"
4) In Link path:, enter node/[nid]

Thanks Graham, your workaround works perfectly. The issue is still present (Views 7.x-3.13). With node/[nid] as a new output, Views transforms the path with the correct language prefix and the pathauto pattern, for example.

#7 seems to do the job.