1. add 'admin_extended' before 'django.contrib.*' and 'admin_tools.*' in INSTALLED_APPS
2. add 'admin_extended.context_processors.settings' in TEMPLATE_CONTEXT_PROCESSORS
3. add 'apptemplates.Loader' in TEMPLATE_LOADERS
Package allow some extra settings to customize - all of them are optional
- ADMIN_JQUERY_ADDITIONAL_VERSION
Is a string which defines additional version of jquery - it will include from google storage
Example: ADMIN_JQUERY_ADDITIONAL_VERSION = '1.9.0'
- FAVICON_PREFIX
Is a string which defines favicon static prefix ('/static/' by default)
Example: FAVICON_PREFIX = '/static/images/'
Also it provides register_url decorator for ModelAdmin or Inline methods. It turns method to view, which returns HttpResponse object.
To use it you should add next line to yours urls.py
url(r'^admin/', include('admin_extended.urls')),
IMPORTANT: it should be placed BEFORE including admin.site.urls, but AFTER admin.autodiscover()
After then you may deco yours methods like that:
class SomeModelAdmin(ModelAdmin):
# finally url will be look like that: r'^/admin/app_label/model_name/extra_url/'
# arg must be a raw string and can not starts with /
# url arg could be omitted - "method_name/$" will be used as url
@register_url(r'extra_url/$')
def get_info(self, request):
return render_to_response('some_template.html')
IMPORTANT: also you must decorate your method with @staticmethod or @classmethod if you use this feture in InlineModelAdmin
NOTE: if you use this feature in InlineModelAdmin, "model_name" still be name of model registred with ModelAdmin which contains inline (so as "app_label").
To prevent it set "use_inline_data" arg to True in register_url decorator
At client side you could use:
- autoinlines.js (a tool to create dynamic inlines, by clicking on checkboxes controllers)
Usage: $.autoInline({
inlineName: "hint",
fields: ["field_name_1", "field_name_2"],
controllers: ["m2m_field_name_1", "m2m_field_name_2"],
requiredMask: 10,
hint: "Check m2m_field_name_1",
empty: "None"
})
- searchline.js (a tool to filter checkboxes)
Usage: $("fieldset .field-fieldname").addSearchLine();
Metadata
Release files for django-extended-admin 1.0.6
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 | Actions |
|---|---|---|---|---|
| django-extended-admin-1.0.6.tar.gz | 6.8 kB | Without provenance | Details for django-extended-admin-1.0.6.tar.gz |
Release files / django-extended-admin-1.0.6.tar.gz
| Download URL | django-extended-admin-1.0.6.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
536a623bba258a5df5ffd62255927e029915b75af8a41ea5ccc0e421ccf01a92
|
|
BLAKE2b-256 checksum How to use checksums |
3f5e279c756b9142a567dc61107fe48b85f9a8799b08b10253408acd28e4cb11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-extended-admin 1.0.6
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.