Introduction
This Plone add-on displays configurable badge that you can use on your development, demo and preview instances. It’ll help you and your customers not to confuse your development Plone instances with production sites.
Compatibility
This add-on was tested for Plone 3 and Plone 4.
Installation
add the following to your buildout configuration file:
[buildout] ... eggs = collective.demositebadge ...
rerun buildout and restart your Zope instance.
then install the collective.demositebadge package from within the portal_quickinstaller tool
Usage
After add-on is install you’ll get Demo site badge Plone Control Panel. There simply enable badge and, if you need, customize default badge text.
That is it.
Usually you’ll have custom theme in your Plone Site, thus you may need to add a bit of css magic in order to make demo badge look better under your own circumstances.
Plone 3 Notes
To install and use this add-on on Plone 3 you need to do some extra steps:
use plone.app.registry fixed versions set; for this add the following to your buildout configuration file:
[buildout] ... extends = http://good-py.appspot.com/release/plone.app.registry/1.0b1 ... [versions] plone.z3cform = 0.6.0 zope.i18n = 3.6.0 [instance] ... zcml = ... plone.app.registryand before Activating demo badge addon, you have to make sure ‘Configuration registry’ is activated (installed) in your Add-ons Control Panel
Live Examples
Credits
Companies
Contributors
Changelog
1.0 - March 16, 2013
Initial implementation. [Victor Imenkov]
Metadata
Release files for collective.demositebadge 1.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 |
|---|---|---|---|---|
| collective.demositebadge-1.0.tar.gz | 16.9 kB | Without provenance | Details for collective.demositebadge-1.0.tar.gz |
Release files / collective.demositebadge-1.0.tar.gz
| Download URL | collective.demositebadge-1.0.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e7fbb7fa47962153db779d28a68c23a9ea9146e7c4b43769b612a349739a713
|
|
BLAKE2b-256 checksum How to use checksums |
31472fd646a101c6938bc3915f83a23b835da7b78ca1a4a6f63ab60c75b31200
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.demositebadge 1.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.