Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#16044 closed Bug (fixed)

"Writing views" documentation reference a nonexistent "previous chapter"

Reported by: aplanas@… Owned by: nobody
Component: Documentation Version: dev
Severity: Normal Keywords: Documentarion
Cc: Triage Stage: Ready for checkin
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Luke Plant)

Reference: http://docs.djangoproject.com/en/dev//topics/http/views/

The last line of the first paragraph of the "Writin views" section assert:

"""For the sake of putting the code somewhere, let’s create a file called views.py in the mysite directory, which you created in the previous chapter."""

I guest that this 'whick you created in the previous chapter' is a C&P error from the book. Maybe the correct line will be more like:

"""For the sake of putting the code somewhere, the recommendation is to put views in a file called views.py, placed in your project or application directory"""

Change History (3)

comment:1 by Luke Plant, 14 years ago

Description: modified (diff)
Summary: "Writing views" documentarion reference a nonexistent "previous chapter""Writing views" documentation reference a nonexistent "previous chapter"
Triage Stage: UnreviewedReady for checkin

Agreed. I fixed some typos in your description, and modified the grammar of your suggestion too, to use 'you' instead of 'we', since 'we' at that point is really only suitable in a tutorial context.

comment:2 by Gabriel Hurley, 14 years ago

Resolution: fixed
Status: newclosed

In [16240]:

Fixed #16044 -- Corrected a copy-and-paste error in the opening paragraph of the views topic guide. Thanks to aplanas for the report and suggested wording.

comment:3 by Gabriel Hurley, 14 years ago

In [16241]:

[1.3.X] Fixed #16044 -- Corrected a copy-and-paste error in the opening paragraph of the views topic guide. Thanks to aplanas for the report and suggested wording.

Backport of [16240] from trunk.

Note: See TracTickets for help on using tickets.
Back to Top