Code

Opened 4 years ago

Closed 3 years ago

Last modified 3 years ago

#12699 closed (fixed)

Possible version/link confusion on the djangoproject.org home page

Reported by: sopor0qv Owned by: justinlilly
Component: *.djangoproject.com Version: 1.1
Severity: Keywords: tutorial links
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

While walking through the tutorial as linked from the djangoproject.org page, I ran into an issue using the csrf_token and found that it wasn't supported in the current official release version of django 1.1.1. I wonder if the link to the tutorial on the djangoproject.org home page should be as follows:

http://docs.djangoproject.com/en/1.1/intro/tutorial01/

instead of:

http://docs.djangoproject.com/en/dev/intro/tutorial01/

Attachments (2)

stableversion.diff (2.2 KB) - added by claudep 4 years ago.
Handle a 'stable' version in djangodocs
stableversion.patch (2.2 KB) - added by claudep 4 years ago.
Handle a 'stable' version in djangodocs

Download all attachments as: .zip

Change History (10)

comment:1 Changed 4 years ago by russellm

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

comment:2 Changed 4 years ago by ericholscher

This probably applies to all the links on the front page, like the installation docs as well?

http://code.djangoproject.com/browser/djangoproject.com/django_website/templates/homepage.html#L43

comment:3 Changed 4 years ago by gabrielhurley

That's sort of an ironic problem, because it will need to be changed *back* to pointing at the 1.2 docs as soon as 1.2 lands... So should the homepage simply be updated manually each time a new version is released?

comment:4 Changed 4 years ago by claudep

I suggest introducing a 'stable' concept, which could be handled in the view of djangodocs (with a corresponding setting).

Changed 4 years ago by claudep

Handle a 'stable' version in djangodocs

Changed 4 years ago by claudep

Handle a 'stable' version in djangodocs

comment:5 Changed 4 years ago by anonymous

  • milestone changed from 1.2 to 1.3

comment:6 Changed 3 years ago by justinlilly

  • Has patch set
  • Owner changed from nobody to justinlilly
  • Status changed from new to assigned

comment:7 Changed 3 years ago by jacob

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

Fixed in recent pushes thanks to Justin Lilly.

comment:8 Changed 3 years ago by jacob

  • milestone 1.3 deleted

Milestone 1.3 deleted

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.