This release is a pre-release and may not be stable for production use.
collective.disableuser
This Plone addon allows a site administrator to block and unblock users.
Features
Block/unblock users through the Plone User controlpanel
Block/unblock users through a REST endpoint
Translations
This product has been translated into
English
German
Installation
Install collective.disableuser by adding it to your buildout:
[buildout]
...
eggs =
collective.disableuser
and then running bin/buildout
Contribute
Issue Tracker: https://github.com/collective/collective.disableuser/issues
Source Code: https://github.com/collective/collective.disableuser
Documentation: https://docs.plone.org/foo/bar
Credits
This plugin is developed and maintained by kitconcept.
If you are having issues, please let us know.
Support
If you are having issues, please let us know via the github issue tracker at https://github.com/collective/collective.disableuser/issues.
License
The project is licensed under the GPLv2.
Contributors
Roel Bruggink, roel@jaroel.nl
Changelog
1.0a1 (2017-04-10)
Initial release. [jaroel]
Metadata
Release files for collective.disableuser 1.0a1
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 |
|---|---|---|---|---|
| collective.disableuser-1.0a1.tar.gz | 16.6 kB | Without provenance | Details for collective.disableuser-1.0a1.tar.gz |
Release files / collective.disableuser-1.0a1.tar.gz
| Download URL | collective.disableuser-1.0a1.tar.gz |
|---|---|
| Size | 16.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fd870e50043716c501ff6da2c08f7aa893769641782ed5a72d31ede416aa165
|
|
BLAKE2b-256 checksum How to use checksums |
df0acbabe3d009ca785e3d6e2c21f3465f8ddff4d1ee5dce66fc15fe4a5244d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.disableuser 1.0a1
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.