How to reproduce:

Create a view with an exposed filter on some field, let's say a textfield.

Let's say you end up with an url like this when running a query in the textfield: ?field_indextitel_value=Rabbit

In my case I'm feeding this "Rabbit" into a contextual filter using "Query argument".

The issue is - this does NOT WORK if the argument is an EXISTING EXPOSED FILTER.

So, for example I have a field_animal_type in an exposed filter of a textfield, and after hitting enter views IGNORES this argument.

BUT - if I change the query manually to ?field_indextitel_valuehello and also set the contextual filter to accept it - it works.

Also notable is that in the preview it works to use the field value as argument.

Thankful for any help on this issue, ideas how to hook it or similar.

Comments

ibuildit created an issue. See original summary.

lendude’s picture

lendude
Primary language Dutch
Location Amsterdam
commented
Project: Views (for Drupal 7) » Drupal core
Version: 8.x-3.x-dev » 8.3.x-dev
Component: Miscellaneous » views.module

Didn't try to reproduce, but can't you change the Filter identifier of the exposed filter to not overlap with the Contextual filter settings? Your steps indicate that this would work as a workaround.

Moving to the right queue.

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Postponed (maintainer needs more info)

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

lamp5’s picture

lamp5
Primary language Polish
Location Rzeszow
commented

I have got the same problem.
Step to reproduce:(i using BEF to change fields widget controls)
-add exposed filter taxonomy term
-add contextual filter by publication year and month

-my nodes for february 2017: url = news/201702
and if i want to sort this results by my taxonomy i can see url with incorrect results
news/all?q=news/201702&field_category_target_id=16

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

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

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

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

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

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

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

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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.

pameeela’s picture

pameeela commented

I am trying to reproduce this but am struggling to understand both use cases listed as there is not a lot of information.

Anyone who is having this issue can you please provide complete steps to reproduce the issue as documented in the linked page.

Specifically here we need to know more about the filter configuration?

pameeela’s picture

pameeela commented
Issue tags: +Bug Smash Initiative

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

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

pameeela’s picture

pameeela commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)