It seems that views query parameters through the URL does not result in them being passed on to the query.

I have narrowed it down to the difference between $view->exposed_data and $view->exposed_input. As far as i can tell from the code, exposed_input is the parameters fetched from either form submission or URL, and exposed_data is only as it is through form submission.

exposed_data is used a couple of places, where it does not make sense to only handle data through form submission.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mian3010 created an issue. See original summary.

mian3010’s picture

Attached proposed solution.

mian3010’s picture

Rookie mistake, sorry.

Lendude’s picture

Status: Active » Needs review

Lets see what the testbot thinks.

Status: Needs review » Needs work

The last submitted patch, 3: views_query_parameters-2841599-3.patch, failed testing.

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

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.

mian3010’s picture

Rerolled patch to apply to 8.3.x

Vinay15’s picture

Status: Needs work » Needs review

@mian3010, When you submit a patch, you need to mark the issue as "Needs review" in the issue metadata for the bot to test it.

Status: Needs review » Needs work

The last submitted patch, 7: views_query_parameters-2841599-4.patch, failed testing.

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

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.

arnested’s picture

Status: Needs work » Closed (works as designed)

This patch has some serious issues breaking other exposed views filters.

I came across this on the project where the patch was initial created to solve a problem. The problem it tries to fix stems from a misunderstanding of views sorting parameters and some not quite consistent fixes on top of that misunderstanding.

I'm closing this as "works as designed".