lineage.controlpanels
Allows Lineage child site specific configurations for plone.registry based controlpanels.
Not available in Lineage Childsites
The following control panels change global settings. Therefore they are not available in subsites.
content-controlpanel
dexterity-types
filter-controlpanel
maintenance-controlpanel
prefs_install_products_form
resourceregistry-controlpanel
security controlpanel
usergroup-groupprefs
usergroup-userprefs
This is also disabled, but should probably fixed to work with local registries too: - portal_registry
This one stores it’s configuration in the registry but has changes one setting in portal_actions, which would affect all sites. Thus disabled. - syndication-controlpanel
Installation
Install lineage.controlpanels by adding it to your buildout:
[buildout]
...
eggs =
lineage.controlpanels
and then running bin/buildout
Source Code and Contributions
If you want to help with the development (improvement, update, bug-fixing, …) of lineage.controlpanels this is a great idea!
The code is located in the github collective.
You can clone it or get access to the github-collective and work directly on the project.
Maintainer is Johannes Raggam and the BlueDynamics Alliance developer team. We appreciate any contribution and if a release is needed to be done on pypi, please just contact one of us dev@bluedynamics dot com
Contributors
Jens W. Klein <jens@bluedynamics.com>
Daniel Widerin <daniel@widerin.net>
License
The project is licensed under the GPLv2.
Contributors
Johannes Raggam <thetetet@gmail.com>
Jens W. Klein <jens@bluedynamics.com>
Daniel Widerin <daniel@widerin.net>
Thomas Massmann <thomas.massmann@it-spir.it>
2.0.0 (2026-03-31)
Internal:
Don’t depend on plone.app.discussion. [thet]
Don’t install the plone.app.discussion controlpanel on Plone 6, if plone.app.discussion is not installed. [thet]
Update configuration files. [plone devs]
Changelog
1.2 (unreleased)
Nothing changed yet.
1.1 (2026-03-31)
pa.discussion is now an core-addon. [jensens]
1.0 (2026-03-31)
Do not autoinclude ZCML. [jensens]
add profile for Plone 6 and fix controlpanel icons. [petschki]
Use tox for testing, ensure tests are passing for Plone 5.0.x, 5.1.x and 5.2.x. [thomasmassmann]
1.0a1 (2016-10-06)
Initial release. [thet]
Metadata
Release files for lineage.controlpanels 2.0.0
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 |
|---|---|---|---|---|
| lineage_controlpanels-2.0.0.tar.gz | 20.9 kB | Without provenance | Details for lineage_controlpanels-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lineage_controlpanels-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for lineage_controlpanels-2.0.0-py3-none-any.whl |
Total release size: 44.0 kB
Release files / lineage_controlpanels-2.0.0.tar.gz
| Download URL | lineage_controlpanels-2.0.0.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0592a743c843be047b9f900184768148dd5c26e03e4e002c547c48cccbd8947b
|
|
BLAKE2b-256 checksum How to use checksums |
759689daec62c25048a255b3ce3fa9c283dca023c0fe7fbbce92a0997e3c19a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / lineage_controlpanels-2.0.0-py3-none-any.whl
| Download URL | lineage_controlpanels-2.0.0-py3-none-any.whl |
|---|---|
| Size | 23.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53f61d184171941284adac9ffa923543e4a8e915c0a62aa119c054d31841dc81
|
|
BLAKE2b-256 checksum How to use checksums |
5e2200449674fe5e463e6ca68bd52fa25f5c37a931b1ff1001820a0b8451671c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for lineage.controlpanels 2.0.0
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.