1. Go to any view that displays a table.
2. Reorder the list by clicking on one of its headers (ID for example) twice.
3. On ajax_views.js you will see that 'settings.view_path' has a wrong path. It will be '/view/ajax' instead of the original view.

This bug effects the $destination variable and therefor it is impossible to redirect back to this view after going to a different page. (For example: when clicking edit button on operation links and editing a specific row, I want to redirect back to the view after clicking save).

CommentFileSizeAuthor
#3 2773229-view-path-save-wrong-path-after-ordering-twice-fix-3.patch513 bytesDavidHalfon

Comments

DavidHalfon created an issue. See original summary.

DavidHalfon’s picture

DavidHalfon commented

I hacked it by adding this line to ajax_views.js:
this.settings.view_path = "/" + this.settings.view_base_path;
Right after (line 82):
this.settings = settings;

DavidHalfon’s picture

DavidHalfon commented
StatusFileSize
new 2773229-view-path-save-wrong-path-after-ordering-twice-fix-3.patch513 bytes

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.

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.

sasanikolic’s picture

sasanikolic commented
Status: Active » Needs review
mbovan’s picture

mbovan commented
Status: Needs review » Closed (duplicate)

This was already fixed in #2820347: Exposed filter reset redirects user to 404 page on AJAX view when placed as a block in 8.8.x-dev branch. The tests will be added in #2866386: Assert the view path is set correctly after second ajax request. Closing this one as a duplicate.