Code

Opened 2 years ago

Closed 2 years ago

#17385 closed New feature (fixed)

Make sure the documentation search version field honor the browsed version.

Reported by: charettes Owned by: nobody
Component: *.djangoproject.com Version:
Severity: Normal Keywords: search documentation version
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

It can get a bit confusing/frustrating to users browsing the documentation for a specific version (say 1.1) to keep switching the search version to the one they're browsing.

I've been bitten by this quite a few times when maintaining a 1.2.X app and I've helped some people on #django irc who we're a bit confused about that.

Attachments (0)

Change History (5)

comment:1 Changed 2 years ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 2 years ago by jezdez

  • Resolution set to fixed
  • Status changed from new to closed

comment:3 Changed 2 years ago by jezdez

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:4 Changed 2 years ago by anonymous

Google seems to prefer the /dev version of the documentation. It should prefer the latest stable version.

Suggestion (using a cookie, e.g. "document_version"):

  • Default to latest stable if no "document_version" cookie — This should keep the latest stable as Google's preferred version
  • If visitor manually selects a different documentation version, set "document_version=X" cookie as a user's preference
  • If visitor loads a page which is not the version they have manually set through the "document_version" cookie, redirect them to desired version using JavaScript

comment:5 Changed 2 years ago by aaugustin

  • Resolution set to fixed
  • Status changed from reopened to closed

Fixed in 82d1ff051b51561806ed027b92619e64af50bebe.

The fix addresses the original problem ie. the search field. I haven't followed the anonymous suggestion.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.