#35747: Admin change list doesn't redirect to default ordering when the last
ordering field is removed from sorting
-------------------------------------+-------------------------------------
Reporter: ldeluigi | Owner: (none)
Type: Bug | Status: new
Component: contrib.admin | Version: 5.1
Severity: Normal | Resolution:
Keywords: admin change list | Triage Stage:
ordering sorting sortremove | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 1
-------------------------------------+-------------------------------------
Old description:
> Basically, when an admin maually clicks on the sortremove link of the
> last remaining field in the sorting query variable, the redirect points
> to an empty string.
>
> For example, if the query parameter is the default `o`, the redirect
> points to `/?o=`, which results in the change list not being ordered at
> all. Instead, I'm claiming that users would expect to see the same
> ordering they experience when landing on the change list page in the
> first place, which was the default ordering, only visible when the
> ordering parameter is absent from the sortremove query.
>
> For this reason, I'd like the sortremove to redirect to `/` instead of
> `/?o=` when the last ordering field would be removed.
>
> I'm opening a PR that *should* do the job.
New description:
Basically, when an admin maually clicks on the sortremove link of the last
remaining field in the sorting query variable, the redirect points to an
empty string.
For example, if the query parameter is the default `o`, the redirect
points to `/?o=`, which results in the change list not being ordered at
all. Instead, I'm claiming that users would expect to see the same
ordering they experience when landing on the change list page in the first
place, which was the default ordering, only visible when the ordering
parameter is absent from the sortremove query.
For this reason, I'd like the sortremove to redirect to `/` instead of
`/?o=` when the last ordering field would be removed.
I'm opening a PR that *should* do the job:
https://github.com/django/django/pull/18558
--
Comment (by ldeluigi):
added link to pr
--
Ticket URL: <https://code.djangoproject.com/ticket/35747#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070191d64ea0de-934240d6-3109-4f4e-aec6-a3f87d6173e7-000000%40eu-central-1.amazonses.com.
