Opened 19 years ago
Closed 18 years ago
#4061 closed (fixed)
Document how to limit access to contrib.databrowse
| Reported by: | bin | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.databrowse | Version: | dev |
| Severity: | Keywords: | databrowse | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
For people that want to limit access to the databrowse contrib, it might make sense to point to the wrapper function at:
Limiting access to generic views
The wrapper could as well contain the register functions.
For example:
# Databrowse wrapper
from django.contrib import databrowse
from django.contrib.auth.decorators import login_required
databrowse.site.register(SomeModel)
databrowse.site.register(SomeOtherModel)
@login_required
def root(*args, **kwargs):
return databrowse.site.root(*args, **kwargs)
Regards,
bin
Attachments (1)
Change History (4)
comment:1 by , 19 years ago
| Component: | Documentation → django.contrib.databrowse |
|---|---|
| Owner: | changed from to |
| Triage Stage: | Unreviewed → Accepted |
by , 18 years ago
| Attachment: | databrowse.diff added |
|---|
patch to Databrowse docs describing how to restrict access to logged-in users
comment:2 by , 18 years ago
| Has patch: | set |
|---|---|
| Summary: | Limiting access to databrowse contrib → Document how to limit access to contrib.databrowse |
| Triage Stage: | Accepted → Ready for checkin |
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This is a bit specific for the docs, considering the docs don't really exist yet, but I guess it'd be helpful to include this.