Introduction
collective.flag is a simple package that adds an option of marking special objects in a Plone site — flagging them. An additional field added to the Settings schemata can be used to differentiate regular documents from the special ones. Possible use-cases:
Put items to the frontpage. Usually not every most recent item should go to the frontpage, but those having a special meaning;
Allow to search for items that are special when building a Collection.
Tips
Rename the field’s title
There is not easy way of renaming field’s title using a controlpanel or something like that. What you can do instead — translate the title using standard mechanisms of Plone.
The recommended solution is to override the translation for the label_flaggedobject_title msgid in the collective.flag domain. Read more about how to do this in Plone 3.x or later here — i18n, locales and Plone 3.0.
Developed by Jarn AS — http://www.jarn.com
Development sponsored by the Bergen Public Library — http://www.nettbiblioteket.no
Changelog
1.3 - March 4, 2013
Support for new-style Collections [mishunov]
1.2 - January 7, 2011
Dutch translation [markvl]
1.1 - 2010-06-30
Sanitized Norwegian translation. [elvix]
Add empty english file to workaround bug in zope.i18n where fallback cannot be english if the catalog does not exist. [gotcha]
Various cleanups. [spliter, hannosch, witsch]
1.0 - 2009-09-08
Initial release [spliter]
Metadata
Release files for collective.flag 1.3
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.flag-1.3.zip | 25.6 kB | Without provenance | Details for collective.flag-1.3.zip |
Release files / collective.flag-1.3.zip
| Download URL | collective.flag-1.3.zip |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
928cd554d87594ab613f68d14b03ae04807280174a672f3b4c411e9cd9e35443
|
|
BLAKE2b-256 checksum How to use checksums |
711473e9a3bdb2ab1c3ef1202f3140bcdb22b15863247290880a69decabfa99a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.flag 1.3
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.