This release is a pre-release and may not be stable for production use.
Introduction
collective.portlet.recentactivity provides a Portlet and a Viewlet with Facebook like entries on recent user activities, e.g. “the user admin added ‘News Item 1’ to ‘News’ 10 minutes ago”.
By default, the Recent Activity Viewlet is not registered. If you want to register it, for example below your content, you have to add this code to your configure.zcml:
<browser:viewlet name="collective.portlet.recentactivity.RecentActivityViewlet" manager="plone.app.layout.viewlets.interfaces.IBelowContentBody" class=".viewlet.RecentActivityViewlet" permission="zope2.View" />
Buildout Installation
To install collective.portlet.recentactivity, add the following code to your buildout.cfg:
[instance]
...
eggs =
...
collective.portlet.recentactivity
...
zcml =
...
collective.portlet.recentactivity
Known Issues
The log entries only work for Archetype content types. Though, it should be fairly easy to replace the Archetype specific event handlers with ones that work for other types of content.
Changelog
1.0b5 (2010-03-31)
Factored out subscriber declarations into its own ZCML file. [timo]
Batch view added to recent activity view. [timo]
Show time column in recent activity view. [timo]
Show 100 recent activity items instead of only 5 in the recent activity view. [timo]
Show user id if no user name is available. [timo]
1.0b4 (2010-02-05)
Fix time not showing up in recent activity Viewlet. [timo]
Show full user name if available. [timo]
Remove ‘User …’ from recent activity Viewlet and Portlet. [timo]
1.0b3 (2010-01-29)
Show a portrait of the user next to the user’s recent activity in the Viewlet. [timo]
1.0b2 (2010-01-27)
Fix “iteration over non-sequence” error, when there are no recent activities. [timo]
1.0b1 (2009-12-11)
Catalan and German translation added. [timo]
Limit for items to show up in viewlet/portlet fixed. [timo]
Bugfix: time was not shown in the recent activity portlet. [timo]
1.0a1 (2009-11-23)
Initial release. [timo]
Metadata
Release files for collective.portlet.recentactivity 1.0b6
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.portlet.recentactivity-1.0b6.tar.gz | 24.2 kB | Without provenance | Details for collective.portlet.recentactivity-1.0b6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| collective.portlet.recentactivity-1.0b6-py2.4.egg | Legacy Egg format | - | - | Details for collective.portlet.recentactivity-1.0b6-py2.4.egg |
Total release size: 66.8 kB
Release files / collective.portlet.recentactivity-1.0b6.tar.gz
| Download URL | collective.portlet.recentactivity-1.0b6.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69c4a1eb862b117b554506632e943f2479e12f6abd1ac8fcaace80aa7a6d1281
|
|
BLAKE2b-256 checksum How to use checksums |
8b40706df1472066f06474c5a86bc1b5a0df484b3e00bbcf5275b619f06bed48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / collective.portlet.recentactivity-1.0b6-py2.4.egg
| Download URL | collective.portlet.recentactivity-1.0b6-py2.4.egg |
|---|---|
| Size | 42.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
4798c9e542ff59b5f84caf8d6c99196e542891b128e39530df728ebbcf638eab
|
|
BLAKE2b-256 checksum How to use checksums |
04e94037f933472190c275b62f4919d3675fd0d55d756eab14e2133380c4aec7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.portlet.recentactivity 1.0b6
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.