Introduction
The user track portlet shows users that are currently active in your Plone site. It uses the plone.validatehook to get information from the Zope webserver.
You can configure the users shown in the portlet using several options:
- timeout
This option determines how long the system will wait before it considers a user to no longer be active.
- roles
With this option you can filter the users shown based on their roles. You can use this to only show editors for example.
- folder_type
This option influences how the role check is done. If you select a content type here the system will walk up through the breadcrumb trail and look for the first item of a selected type. The roles of the user at that location will be used when applying the roles check.
Caveats
The default configuration uses a global dictionary through DictStorage for storing userinformation. This will not work with multiple ZEO clients in separate processes that don’t share this dictionary. To use the usertrack portlet with a ZEO setup, install memcached and use the “MemcacheStorage” by using the following zcml snippet in an overrides.zcml somewhere:
- <utility
factory=”collective.portlet.usertrack.storage.MemcacheStorage” provides=”collective.portlet.usertrack.interfaces.ITrackerStorage” />
Changelog
1.1.1 (2013-11-10)
Fixed a bug where in some cases on some Plone versions you can get an error on loading the ZCML because of a missing permission.
1.1 (2013-07-08)
No changes since beta.
1.1b1 (2013-06-25)
The portlet now links each user to the users author page.
1.0 - October 26, 2010
Fix improper check on portal type in usertrack.py
Implement ZEO support through different storages, specifically through the MemcacheStorage. The traditional behaviour is preserved through the DictStorage which is still the default. [ivo] 2009-05-24
Fix bad spelling in portlet CSS class name.
To avoid confusion, add “.dev” suffix to version.txt as long as a new version is not released. [kdeldycke] 2009-05-12
Add french translation. [kdeldycke] 2009-04-23
Add Spanish translation.
Add Master Template translation. [macagua] 2009-02-17
1.0a1 - August 1, 2008
Initial release. [wichert]
Metadata
Release files for collective.portlet.usertrack 1.1.1
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 | |
|---|---|---|---|---|
| collective.portlet.usertrack-1.1.1.zip | 30.6 kB | Without provenance | Details |
Release files / collective.portlet.usertrack-1.1.1.zip
| Download URL | collective.portlet.usertrack-1.1.1.zip |
|---|---|
| Size | 30.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dbbd247bc4a822fc8d0d1818f0a89bf8cc9aa4e640ca13348a0c714e832cec35
|
|
BLAKE2b-256 checksum How to use checksums |
aa016f6cbaffb584a44184fbc45d4b873f824ebf071307e447f707ff5c61976d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.portlet.usertrack 1.1.1
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.