djangocms-concurrent-users
A Django-CMS plugin for blocking pages which are edited by another user. This provides a simple mechanism to prevent two users working on the same page. Due to the fact, that only the version of the last user hitting the save button is stored, data loss is very likely.
This plugin adds a hidden toolbar item in order to provide the required code to the client. Once the browser enters a page, it checks for another user and gets blocked in case the page has been locked. If the page is not edited at this moment, the client acquires a lock and hence blocks it for other users for the time of working. The check if performed by polling the server with an specified interval. Once the client lefts the page, the lock is released and the next user will be able to make changes.
Features
blocks a page with an overlay in case another user is already working on it
reloads the page once it is released, in order to fetch the latest changes
displays the username and time of the blocking user
Installation
To get started using djangocms-concurrent-users:
install it with pip:
$ pip install djangocms-concurrent-users
add the plugins to INSTALLED_APPS:
INSTALLED_APPS = ( ... 'djangocms-concurrent-users', ... )run migrate.
add url(r'', include('djangocms_concurrent_users.urls', namespace='concurrent_users'), ), to your urls
Configuration
CONCURRENT_BLOCKING_OFFSET: Time to wait until the page is release just after the user left; is 20 by default; Must not be shorter than CONCURRENT_POLLING_INTERVAL
CONCURRENT_POLLING_INTERVAL: Interval for the clients to poll the server; is 20 by default; Must not be greater than CONCURRENT_BLOCKING_OFFSET
CONCURRENT_BLOCK_EDITING: Specifies if the blocking actually happens; is True by default;
Metadata
Release files for djangocms-concurrent-users 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| djangocms_concurrent_users-0.0.5-py2-none-any.whl | Python 2 | none | any | Details for djangocms_concurrent_users-0.0.5-py2-none-any.whl |
Release files / djangocms_concurrent_users-0.0.5-py2-none-any.whl
| Download URL | djangocms_concurrent_users-0.0.5-py2-none-any.whl |
|---|---|
| Size | 631.7 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
fe1412f5dd797e6372e91d9e7b79a48a88e20cdb0aae4fa0699e8e41dbae2b9b
|
|
BLAKE2b-256 checksum How to use checksums |
1c767f5c853e95c38e96c04a1431bf81198ffd2b24dbd77f506c9a7c5898e709
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for djangocms-concurrent-users 0.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.