This package provides a control panel to configure in which language do you want to show the admin interface.
This is useful if you need to configure a website in a language you don’t know.
This package is based in Silvuple a package that use to do this and more for Plone 3.
Installation
Install cs.adminlanguage by adding it to your buildout:
[buildout]
...
eggs =
cs.adminlanguage
and then running bin/buildout. Then start Plone and activate the add-on in the Add-ons control panel.
Now you can go to the Language Admin Settings control panel from this add-on and set the preferred admin language. This language will be used for all translation messages in domains that start with “plone” or “collective” (or the “linguaplone” domain).
Now any authenticated user with the “cs.adminlanguage: ViewinAdminLanguage” permission will see messages from those domains in the chosen admin language. The suggested way for configuring this, is to go to the Groups control panel, select the Administrators and Site Administrators groups, and grant them the AdminLanguageReader role.
Contribute
Issue Tracker: https://github.com/codesyntax/cs.adminlanguage/issues
Source Code: https://github.com/codesyntax/cs.adminlanguage
Support
If you are having issues, please let us know adding an issue in Github
License
The project is licensed under the GPLv2.
Contributors
Lur Ibargutxi, libargutxi@codesyntax.com
Maurits van Rees, maurits@vanrees.org
Mikel Larreategi, mlarreategi@codesyntax.com
Peter Mathis, office@kombinat.at
2.0 (2026-08-12)
Breaking changes:
Replace pkg_resources namespace with PEP 420 native namespace. (#3928)
Internal:
Update configuration files. [plone devs]
1.1 (2025-01-23)
Bug fixes:
Fix None type request. [petschki] (#4)
Internal:
Update configuration files. [plone devs]
1.0 (2024-12-11)
Internal:
Initial release. [libargutxi]
1 maintainer
Metadata
1 maintainer
Release files for cs.adminlanguage 2.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 |
|---|---|---|---|---|
| cs_adminlanguage-2.0.tar.gz | 22.0 kB | Without provenance | Details for cs_adminlanguage-2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cs_adminlanguage-2.0-py3-none-any.whl | Python 3 | none | any | Details for cs_adminlanguage-2.0-py3-none-any.whl |
Total release size: 44.1 kB
Release files / cs_adminlanguage-2.0.tar.gz
| Download URL | cs_adminlanguage-2.0.tar.gz |
|---|---|
| Size | 22.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6bf8cabe63def203b8328f1d1f4594eac3b18fa75bb7088a1d92d7d5c2c3983f
|
|
BLAKE2b-256 checksum How to use checksums |
77fdd0d1c5f2a85b5f664b362e79a3bfbaf6f2d91f62fcf0f214d13520a3d188
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Release files / cs_adminlanguage-2.0-py3-none-any.whl
| Download URL | cs_adminlanguage-2.0-py3-none-any.whl |
|---|---|
| Size | 22.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94019bb1627fc45b42f527963661b11726527b597b38ac8b9ae9db22558578f8
|
|
BLAKE2b-256 checksum How to use checksums |
3c3d11d60e5a04cd422b675b6f0e2a946693bc2f2000dbd1dcebde85b55f4cca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Security for cs.adminlanguage 2.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.
