Problem/Motivation

Given a view that has two sorts: 1. A non-exposed sort on field foo that sorts DESC. 2. An exposed sort on field bar that sorts ASC by default.

The expected default sort (i.e. without any query arguments in the request) would be: foo DESC, bar ASC

The actual default sort is: foo DESC, bar DESC

In other words, the sort order of the exposed sort is being set incorrectly, in fact it is being taken from the non-exposed sort (thus to expose this bug the sort orders must be different).

The problem is that \Drupal\views\Plugin\views\exposed_form\ExposedFormPluginBase::exposedFormAlter() uses the configured sort order of the first sort plugin as the default sort order, when it should be using the configured sort order of the first exposed sort plugin.

Proposed resolution

Fix \Drupal\views\Plugin\views\exposed_form\ExposedFormPluginBase::exposedFormAlter() to use the correct sort order.

Remaining tasks

Update the patch
Write tests.
Review patch.

User interface changes

None.

API changes

None.

Data model changes

None. This does not change the Views configuration, it only has an effect during runtime.

Issue fork drupal-2737395

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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tstoeckler created an issue. See original summary.

tstoeckler’s picture

Status: Active » Needs review
FileSize
1.22 KB

Here we go. This fixes the issue for me. Needs a test of course.

tstoeckler’s picture

Here's a test. If we had a nicely decoupled test suite I would have added a dedicated test method for this, but there is only a single test class for all of the views exposed form stuff, so adding this little bit seemed fair in this case.

Also the test view was not up to snuff anymore (as clearly visible by the dependency on node), so updating that. I added the additional sort in the UI and then exported.

The last submitted patch, 3: 2737395-3--tests-only.patch, failed testing.

Status: Needs review » Needs work

The last submitted patch, 3: 2737395-3.patch, failed testing.

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

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

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

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.

kducharm’s picture

Status: Needs work » Needs review
FileSize
4.43 KB

Re-roll of patch for 8.5.x, confirmed the patch does set the order correctly but I'm not very familiar with the test so someone else should probably review that.

Status: Needs review » Needs work

The last submitted patch, 10: 2737395-10.patch, failed testing. View results

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.

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

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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.

Version: 8.8.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. 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.

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.

quietone’s picture

Issue summary: View changes
Issue tags: +Bug Smash Initiative, +Needs reroll

I tested this on Drupal 10.1.x, umami install and was able to reproduce the problem. I then copied the few lines of the patch to ExposedFormPluginBase and retested. The changes suggested fix the problem in the Issue Summary,

ameymudras’s picture

Version: 9.5.x-dev » 10.1.x-dev
Status: Needs work » Needs review
FileSize
4.53 KB

Re rolled to 10.1.x

Status: Needs review » Needs work

The last submitted patch, 20: 2737395-20.patch, failed testing. View results

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

sahil.goyal’s picture

trying to resolve the error and uploading interdiff.

Version: 10.1.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, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

vsujeetkumar’s picture

Need re-roll againts 11.x.

vsujeetkumar’s picture

Re-roll patch created, Keeps as "Needs Work", having some fail tests.