"Remember" feature of exposed filters doesn't work with AJAX and is generally fragile

I'm seeing this in the latest 7.x-3.x-dev version, too. Any fix approach for this? Glad to help if I can.

Changed instruction to reproduce

I've also tried this feature in views 7.x-3.11
But there is no results. Same problem occurs again.

Doesn't look like anyone has looked at this for 4 years #6,so i wouldn't get my hopes up that it will be fixed!

If you turn off ajax then edit your exposed filter and check "Remember last selection" the view should remember the selection when you go back.

This is still a problem in drupal 8......

Is there any workaround for this bug in Drupal 7 so I can still use AJAX and Views exposed filters? Both are important for the app I'm building. Some way to store the filter parameters and resubmit them on page load, like a session, or cookie? Even something that would reset the state of the filter parameters when loading the page, so the state of the filters matched the returned results, would be better than nothing...

Any news for 2018 now? It's still not working properly in version 8. It seems to be remembered properly, but it isn't shown in the ajax Page. Maybe it's just a caching issue...

changed version while the issue still applies on 8.x views

Moving to the right queue.

Hello yes I can also confirm this issue.

It is easy to reproduce. I was debugging with ?XDEBUG_SESSION_START at the end of the URL, and simply adding this will cause the bug, the remember-me option will stop working :)

Hello,

After some debugging I have found that the issue comes from 'core/modules/views/src/ViewExecutable.php' :

public function getExposedInput() {
     
     [...]

      // If we have no input at all, check for remembered input via session.

      // If filters are not overridden, store the 'remember' settings on the
      // default display. If they are, store them on this display. This way,
      // multiple displays in the same view can share the same filters and
      // remember settings.
      $display_id = ($this->display_handler->isDefaulted('filters')) ? 'default' : $this->current_display;

      if (empty($this->exposed_input) && !empty($_SESSION['views'][$this->storage->id()][$display_id])) {
        $this->exposed_input = $_SESSION['views'][$this->storage->id()][$display_id];
      }
    }

    return $this->exposed_input;
  }

The comment says "If we have no input at all, check for remembered input via session". When there are $_GET parameters which are not 'page' nor 'q' (both of which are removed a little bit before in the code), then $this->exposed_input is not empty and the values from $_SESSION are not used any more.

The question is why $_SESSION values must only be used when there are no other input ? Wouldn't it be possible to merge (possible) $_SESSION values with current $_GET parameters ? in case of conflict, $_GET parameters should take precedence.

Otherwise this bug happens, meaning that $_SESSION information is not recovered and 'remember' settings will be lost on the next page load.

Following, so are there any solutions for this?

Here is a fix I worked up that seems to work. It basically checks to see if we have ajax request and then skips restoring the values from the session.

I had this same issue and tried the patch in #17. It didn't quite work, it would remember the first value the user chose and that would persist no matter what choices were made after that. This module solved the problem for me and might help someone else: https://www.drupal.org/project/views_ajax_history

Ran across this issue, would be so incredibly helpful if this was fixed in Core so that contrib projects like Better Exposed Filters, Views AJAX History, etc. are not required in order to achieve this functionality.

Closed #2904491: Views doesn't re-apply its AJAX filters when going back to a page as a duplicate and added contributors to this issue.

Agree with #21, its better to include this contrib projects inside the Drupal core. Its better because its logically to go back to the last current state of the view (when you hit the browser back button).

Patch #17 will apply to Drupal 9.1.8 but unfortunately it does not solve the problem for me. Nor will the Views AJAX History module. Both together doesn't help either. I just can't get filter "remembering" to work.

For me its working when the view has caching disabled.

What works for me, oddly, is turning off AJAX on the view but still having BEF on. I still get the ajax submits, and don't get the errors with remembering.

Adding related issue that may have fixed this.

The next step here is to confirm that this is still a problem. I am adding the tag for manual testing and updating the Issue Summary to add that as a remaining task.

Cheers

Since there hasn't been a follow up to #36 going to close out for now.

If still a bug please reopen.

Thanks all!