django-ticker
django-ticker is a reusable Django application that provides a ticker like news section including row level permissions. What does this mean?
In django-ticker you have a fine grained permission control what the (administrative) user can do and what not. Besides the default Django permissions – add, change, delete – there are some extra permissions:
change_foreign
publish
Originally this was created for the news section of the German Django community where foreign users could add articles but had no permission to publish them, cause a moderator must check these articles first.
It’s easy to create a pressroom like workflow, assumed we have different people with different permissions:
- The freelance journalist:
Granted permissions: add, change
can add articles
can change his articles (only his own)
can not delete his articles
can set the status of the article to “closed” or “draft”. Draft means, that the article is ready for check by a moderator.
in the admin list of articles, they see only they own
- The journalist:
Granted permissions: add, change, delete, publish
can add articles
can change and delete his articles (only his own)
can set the status of the article to “closed”, “draft” or “published”
in the admin list of articles, they see only their own
- The chief editor (or moderator):
Granted permissions: add, change, delete, publish, change_foreign
can add articles
can change and delete all (!) articles
can set the status of the article to “closed”, “draft” or “published”
in the admin list of articles, they see all articles
- The proofreader (or subject specialist):
Granted permissions: change, change_foreign
can not add articles
can not delete articles
can not publish articles
can change all articles (e.g. for correction)
in the admin list of articles, they see all articles
So, you can mix these permissions and create a workflow that perfectly fits your needs.
Metadata
Release files for django-ticker 0.2.1
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-ticker-0.2.1.tar.gz | 8.0 kB | Without provenance | Details for django-ticker-0.2.1.tar.gz |
Release files / django-ticker-0.2.1.tar.gz
| Download URL | django-ticker-0.2.1.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11eae5ffce0b421232ce1f9e50a5c9a164d6c31bd15f4ba6a2c2c264370b7b13
|
|
BLAKE2b-256 checksum How to use checksums |
ce2615b4015f81508079700015e87ca49134e19dd4da8e2d7e4e8afac83c8f2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-ticker 0.2.1
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.