Hi,

I have a site with two languages installed and no translation. If I create a view with a contextual filter on the content language I can provide single arguments de or en for the view and get the nodes in that language in return. If I try to combine the two filters de+en I get no results. I would expect this to work like taxonomy where I can user multiple arguments to get my nodes.

Issue fork drupal-2985585

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

rogerpfaff created an issue. See original summary.

rogerpfaff’s picture

I've tested on simlytest.me with a standard drupal installation.

1. Create a second language
2. Create content in two languages
3. Create a view for the content
4. Add contextual filter language and try filtering

The SQL that is created at this point looks like this

SELECT node_field_data.created AS node_field_data_created, node_field_data.nid AS nid, node_field_data.langcode AS node_field_data_langcode
FROM 
{node_field_data} node_field_data
INNER JOIN {node} node ON node_field_data.nid = node.nid
WHERE (node.langcode = 'de+en') AND ((node_field_data.status = '1') AND (node_field_data.type IN ('article')))
ORDER BY node_field_data_created DESC
LIMIT 11 OFFSET 0

Obviously the langcode does not get expanded to the single values in the WHERE condition.

In the past there was an option in views to handle multiple arguments and this option is gone now.

rogerpfaff’s picture

rogerpfaff’s picture

Version: 8.5.5 » 8.5.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.5.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

inge_dt made their first commit to this issue’s fork.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.