#32878 closed Cleanup/optimization (invalid)
Seems that browsing releases in Django Project website interchanged "Prev" and "Next" links
| Reported by: | Igor Kuivjogi Fernandes | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 3.2 |
| Severity: | Normal | Keywords: | links releases |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I was navigating inside the 3.2.4 release (https://docs.djangoproject.com/en/3.2/releases/3.2.4/) and found something in the sidebar at Browse section:
- the Prev link leads to 3.2.5 release
- the Next link leads to 3.2.3 release
Should not it to be the opposite, i.e., Prev leads to 3.2.3 and Next leads to 3.2.5 ?
Attachments (1)
Change History (3)
by , 3 years ago
| Attachment: | django-releases.png added |
|---|
comment:1 by , 3 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Thanks for the report, however as far as I'm aware it's not something that we can change (Sphinx builds docs that way). Release are sorted like this to keep the latest version at the top, see Release notes.
comment:2 by , 3 years ago
The release notes are listed from newer to older releases, see https://docs.djangoproject.com/en/stable/releases/. As such, when viewing the release notes for 3.2.4, the previous page is for 3.2.5 and the next page is for 3.2.3.
The previous and next links at the bottom of the page and in the sidebar are moving backward and forward between documentation pages and are not specific to the release note pages, nor release versions. I can see how this may be confusing when looked at only in the context of the releases, but it is not possible to change without reordering the release notes to be in non-reverse order.
Browsing releases