Opened 14 years ago
Closed 10 years ago
#14664 closed New feature (fixed)
MiddlewareNotUsed should display a warning
Reported by: | teserak | Owned by: | nobody |
---|---|---|---|
Component: | Core (Other) | Version: | dev |
Severity: | Normal | Keywords: | sprintdec2010 |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
MiddlewareNotUsed should display a warning.
Warning could contain middleware_path and user message if it's defined.
For example:
MiddlewareNotUsed("Online users middleware supports only database session engines."))
display:
MiddlewareWarning: users.middleware.OnlineUsers. Online users middleware supports only database session engines.
Change History (7)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Keywords: | sprintdec2010 added |
---|---|
milestone: | 1.3 |
Triage Stage: | Unreviewed → Accepted |
This would be reasonable if DEBUG=True. This is a feature request, so removing from the 1.3 milestone which is now focused on bug fixing.
comment:3 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → New feature |
comment:6 by , 10 years ago
Has patch: | set |
---|---|
Version: | 1.2 → master |
I've logged a warning instead of adding a new warning class to be consistent with the rest of the file.
comment:7 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
when do you think it would be necessary?
It would log the message with DEBUG=TRUE or DEBUG=FALSE?