[patch] Save Filtering List Views in Admin into Session

[anonymous]

Another minor, but useful addition - when someone filters a list of objects in the admin, then edits one, then goes back to that list of objects, it would be nice if this filtering would be saved in the session so that it can span across pages. Many times people still want to see the same filtering on the object list page.

[arnaud AT pimentech DOT net]

Propagates filter values (in GET) when editing or adding an object in admin

[arnaud AT pimentech DOT net]

I just added a patch to propagate filters as GET values when editing or adding an object in admin.

I don't think a hybrid version using both session and GET values is really practical. Maybe we should change the filter system to be session-only, but I'm not sure this is such a good idea. This would allow us to store filters on a per-model basis, though.

[Jacob]

At some point, we'll be reworking the admin interface, and this will be one of the things we examine at that time.

[mrts]

Probably not in scope for 1.0.

[Karen Tracey]

#9467 is another request for this ability.

[jacmkno]

Some thoughts:
Session based filters is not an option. The option of sharing the URL to a filtered listing is a great functionality that cannot be lost.
In addition to preserving the filters after editing or adding, the fields in the add form should be pre-filled according to the filters applied.
(But that could be a separate ticket).

[jacmkno]

Maybe the filters can be saved into the session but they have to come back into the URL after editing or adding. This sounds as a good solution.

In the session the admin could have a dictionary with applied filters for each model. When the users go to the model record listing page, the admin detects 2 things:

1. The comming request does not apply any filters
2. There are some filters applied to the requested model in the session

In that case the admin can make a redirection to the same listing but putting all the session filters inside the URL as they normally are.
There should also be an extra control paramenter like: no_session_filters=1, and if that parameter comes in the request the admin does not make the redirection.

This sounds like a clean solution to me.

[(none)]

Milestone post-1.0 deleted

[alTus]

This patch isn't up-to-date.
Could someone provide a new one or at least give some recomendations how to get such functionality?

[Ramiro Morales]

Wait, this is a duplicate of #6903 that has an up-to-date patch. The current implementation there stored uses URL query strings to persist the filter status instead of sessions but the discussion in the ticket and in the associated mailing thread proposes also using session.