Nested inline support for Django admin
Most of the code from this package is from [https://code.djangoproject.com/ticket/9025](https://code.djangoproject.com/ticket/9025)
Github
[https://github.com/soex0101/django-nested-inline-bug-fixed](https://github.com/soex0101/django-nested-inline-bug-fixed) Forked from [https://github.com/s-block/django-nested-inline](https://github.com/s-block/django-nested-inline)
Installation
pip install django-nested-inline-bug-fixed
Usage
Add nested_inline to INSTALLED_APPS
models.py
from django.db import models
- class TopLevel(models.Model):
name = models.CharField(max_length=200)
- class LevelOne(models.Model):
name = models.CharField(max_length=200) level = models.ForeignKey(‘TopLevel’)
- class LevelTwo(models.Model):
name = models.CharField(max_length=200) level = models.ForeignKey(‘LevelOne’)
- class LevelThree(models.Model):
name = models.CharField(max_length=200) level = models.ForeignKey(‘LevelTwo’)
admin.py
from django.contrib import admin from nested_inline.admin import NestedStackedInline, NestedModelAdmin from example.models import *
- class LevelThreeInline(NestedStackedInline):
model = LevelThree extra = 1 fk_name = ‘level’
- class LevelTwoInline(NestedStackedInline):
model = LevelTwo extra = 1 fk_name = ‘level’ inlines = [LevelThreeInline]
- class LevelOneInline(NestedStackedInline):
model = LevelOne extra = 1 fk_name = ‘level’ inlines = [LevelTwoInline]
- class TopLevelAdmin(NestedModelAdmin):
model = TopLevel inlines = [LevelOneInline]
admin.site.register(TopLevel, TopLevelAdmin)
Changelist
0.4.4 - Add formset:added and formset:removed events (#97)
0.4.3 - Update media so it expects to find jquery in the right place. (#75)
0.4.2 - Fix assets
0.4.1 - Fix permission checks
0.4.0 - Added support for Django 3.0
0.3.7 - added support for django 1.10, fix unique fieldset id
0.3.6 - added support for django 1.9
0.3.5 - Removed deprecated methods and updated for Django 1.8/1.9
0.3.4 - added licence and updated for python 3
0.3.3 - fixed bug where inlines without inlines would cause an error
Metadata
Release files for django-nested-inline-bug-fixed 0.4.4
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-nested-inline-bug-fixed-0.4.4.tar.gz | 18.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_nested_inline_bug_fixed-0.4.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.0 kB
Release files / django-nested-inline-bug-fixed-0.4.4.tar.gz
| Download URL | django-nested-inline-bug-fixed-0.4.4.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
262004fcb868bafcd26d62217be61470cfe59348b57b801e4dbba41c76df24fc
|
|
BLAKE2b-256 checksum How to use checksums |
245552e6b7aa803bd2644ce39d316201579c8740cc8e2c830f206e110825fd59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.4
|
Release files / django_nested_inline_bug_fixed-0.4.4-py3-none-any.whl
| Download URL | django_nested_inline_bug_fixed-0.4.4-py3-none-any.whl |
|---|---|
| Size | 23.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
221024aea7bf8412f91522a7d8968dd0069b0337319e3769144ab70da7c0fd1c
|
|
BLAKE2b-256 checksum How to use checksums |
0b72b109e9759df675ea6666115e00cfd7270b832f63144a88fa345e5acde390
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.8.2 pkginfo/1.8.2 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.7.4
|
Security for django-nested-inline-bug-fixed 0.4.4
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.