Opened 11 years ago

Closed 10 years ago

Last modified 9 years ago

#12327 closed (wontfix)

Internationalization documentation specifies common middleware after session middleware

Reported by: portante Owned by: nobody
Component: Documentation Version: 1.1
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


See the topic, How Django Discovers Language Preference. There is box that shows an example of where to locate the LocaleMiddleware, properly following SessionMiddleware, but listing CommonMiddleware last.

In the middleware documentation, CommonMiddleware is shown listed first. Is there any reason why CommonMiddleware must come first or last in either of these cases?

A note clarifying any dependencies or documenting that there are no dependencies might be helpful.

Change History (2)

comment:1 Changed 10 years ago by Russell Keith-Magee

Resolution: wontfix
Status: newclosed

There's no reason that CommonMiddleware should go first or last. Like most middlewares, it has no dependencies, which is why the middleware documentation doesn't mention any. There are only a couple of middlewares that are order specific - LocaleMiddleware being one of them.

comment:2 Changed 9 years ago by Jacob

milestone: 1.2

Milestone 1.2 deleted

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