django-admin-customizer
Django admin customizing interface
Features
Multiple admin instances for the same model
Customization of:
list_display
list_filter
raw_id_fields
search_fields
TODO
actions configurator
base admin class support
Requirements
Django 1.2, 1.3, 1.4, trunk. Django 1.1 is NOT supported.
Python 2.6 or 2.7
Installation guide
Install from pypi, with pip:
pip install django-admin-customizer
Or with setuptools:
easy_install django-admin-customizer
Add admin_customizer to INSTALLED_APPS:
INSTALLED_APPS += ("admin_customizer", )
Add the admin customizer’s urls to your root url conf. This is the url where your will access your custom admin instances. Eg: in your project’s urls.py add:
(r'^admin/_/', include('admin_customizer.urls')),
After that you need to run:
manage.py syncdb
Or if you use south:
manage.py syncdb --migrate
You need to update admin_customizer’s models to get it working, initially and after each model change with:
manage.py refresh_available_fields
Note:
If you delete models the registered admins will be deleted for them.
If you delete fields from models the registered admins will have them removed after you run refresh_available_fields.
django-admin-customizer has static files for widgets in the edit interface. If you use staticfiles just run:
manage.py collectstatic
If you do not use django.contrib.staticfiles you must manually symlink the site-packages/admin_customizer/static/admin_customizer dir to <your media root>/admin_customizer.
Making extra actions available
TODO
Settings
ADMIN_CUSTOMIZER_MAX_FIELD_DEPTH - depth to look for relations when inspecting models.
Middleware
To enable urlpattern reloading add 'admin_customizer.middleware.URLResolverReloadMiddleware' to MIDDLEWARE_CLASSES.
Warning!
You must have working django cache for this to work properly ! See django’s cache documentation on this.
If you do not enable this you will have to restart the webserver after every AdminSite or RegisteredModel change !
Screenshots
Edit page:
Metadata
Release files for django-admin-customizer 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-admin-customizer-0.2.tar.gz | 52.4 kB | Without provenance | Details |
Release files / django-admin-customizer-0.2.tar.gz
| Download URL | django-admin-customizer-0.2.tar.gz |
|---|---|
| Size | 52.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d9ac40dc08015482e343554b1703b4a1cb6186237931ba6d21805b642601c1e1
|
|
BLAKE2b-256 checksum How to use checksums |
376850cce5f12025b28f9d6b3cc02075ea22d5395d64841a5e62a65800966a0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-admin-customizer 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.