Introduction
StickyStatusMessages provides persistent status messages.
Normal status messages usually appear when a content item has been affected (created, edited, removed, state changed etc.) in some way. They appear to the user effecting the change.
In the case of StickyStatusMessages, status messages now also appear to other users, who have an interest (or stake) in the same content item. The other users who are notified, are the ones with a local ‘Editor’ role on the object being affected. Since the original editor or owner who did the change by himself he personally will NOT get a sticky statusmessage.
They will receive a notification message (very similar to the existing status messages) above the portal content, every time a content item (on which they have the Editor role) has been changed.
These messages are ‘sticky’ in the sense that they are persistent. They have to be removed manually by the user. This is very easy though, you simply click on the [X] sign on the message itself and it will be removed.
Changelog
0.4 (2012-03-21)
Play nicely when not installed. Check if the browserlayer is installed before continuing. [jcbrand]
Added an adapter for the notification mechanism. Enables CMFNotification integration. [isburger]
Check for attribute error if running with testrunner request
0.3 (2011-09-13)
Tested in Plone 4.1 (jcbrand)
0.2 (2011-04-04)
Fixed IE javascript bug #2038 (deroiste)
0.1 (2010-10-04)
Improved error handling (pilz, jcbrand)
Improved handling of non ascii chars (jcbrand)
Removed babble dependencies (jcbrand)
Allow for people to remove all sticky messages(jcbrand)
0.1a1 (2010-04-20)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for slc.stickystatusmessages 0.4
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 |
|---|---|---|---|---|
| slc.stickystatusmessages-0.4.zip | 27.0 kB | Without provenance | Details for slc.stickystatusmessages-0.4.zip |
Release files / slc.stickystatusmessages-0.4.zip
| Download URL | slc.stickystatusmessages-0.4.zip |
|---|---|
| Size | 27.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d05c9e1f31fab2c4eed3a83b64a1923a1918b9bd142a53a37b787efdda32bf7
|
|
BLAKE2b-256 checksum How to use checksums |
3254132e73c85768528b3ef0258ef11570f0c3780c0fdd519fad65d36f0e78d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for slc.stickystatusmessages 0.4
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.
