Problem/Motivation

"Rendering language" setting of Views does not respect when using "Make field dependent using views" for children field.
This problem does not occur with ajax update, but only once when the edit form is loaded.

label is not translated on child filed

Similar issue: https://www.drupal.org/project/drupal/issues/2174633

Steps to reproduce

1. Enable language, content translation, interface translation module
2. Add some language such as Japanese ('ja')
3. Create some taxonomy terms and its translation
4. Create term reference view with "Rendering language" set to "Interface text language selected for page" by Views
5. Edit the children field settings and select the "Make field dependent using views" option on the Reference type, and select view that created by previous step on the "View used to select the entities".
6. Create a new node with fill in parent field and child field.
7. Open edit form of node with non-default language (ex. /ja/node/edit/1)
8. You can see the children field is not translated.

Proposed resolution

Display the string through `ViewsRenderPipelineMarkup` as a label to repect "Rendering language" setting of Views.

Remaining tasks

None

User interface changes

None

API changes

None

Data model changes

None

CommentFileSizeAuthor
dependent_field_not_translated.png162.19 KBblauerberg
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

blauerberg created an issue. See original summary.

blauerberg’s picture

Issue summary: View changes
blauerberg’s picture

Status: Active » Needs review
pcambra’s picture

Issue tags: +Needs tests
pcambra’s picture

Status: Needs review » Needs work
pcambra’s picture

Version: 1.0.1 » 1.x-dev
Status: Needs work » Fixed

Thanks!!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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