Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Introduction

This package provides some enhancements to Plone’s standard commenting functionality. It attempts to keep as much of the existing commenting machinery as possible, but adds the following features:

Events:

  • An IObjectAddedEvent is fired when a discussion item (described by the interface Products.CMFCore.interfaces.IDiscussionResponse) is created.

  • Similarly, an IObjectRemovedEvent is fired when a discussion item is deleted.

Indexing:

  • Content items gain two additional catalogue indexes: number_of_comments, which contains the number of comments left on a content item, and commentators, which contains a list of unique usernames of those who have left one or more comments on the content item. number_of_comments is also available as catalogue metadata.

  • Collections are configured so that it is possible to search by these indexes. For example, the ‘Current author’ criterion can be used to list all content items upon which the current user has left a comment.

  • Discussion items gain an additional catalogue metadata column, comment_subject, which contains the title of the content item that was commented upon (note that this is not updated if the content item changes title).

Workflow:

  • Discussion items will respect the workflow set in portal_workflow. By default, the one_state_workflow is used, which means a comment is always published. An additional comment_review_workflow is installed, which has two states: pending and published. Comments may either be published or deleted.

  • A new view, @@review-comments, is available for any folder or the portal root. This allows site-wide (or folder-wide) moderation of comments, with quick publish/delete operations.

Note that the @@review-comments view makes a few assumptions:

  • Comments pending review are always in the pending state. You can add a review_state request parameter to specify a different state to search for, however.

  • There is a transition called publish to move a comment from pending to published. You can request a different transition by providing a request parameter publish_transition.

Furthermore:

  • The number_of_comments index will only include comments in the published state.

  • Neither the portal_catalog Clear and rebuild, nor the portal_workflow Update security settings operation will correctly find and update comments, due to the way that comments are stored.

Requirements

This product requires Plone 3.3+ (and will likely not work with Plone 4). In particular, it relies on plone.indexer, which is part of Plone 3.3+.

Changelog

1.0b2 - 2009-04-17

  • Catch up to Plone 3.3

Metadata

Release files for collective.discussionplus 1.0b2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for collective.discussionplus 1.0b2
File Size Uploaded Provenance Actions
collective.discussionplus-1.0b2.tar.gz 18.9 kB Without provenance Details for collective.discussionplus-1.0b2.tar.gz

Release files / collective.discussionplus-1.0b2.tar.gz

Download URL collective.discussionplus-1.0b2.tar.gz
Size 18.9 kB
Tags Source
SHA-256 checksum
How to use checksums
ef78cac70193816d2e2c666b102efed01e285d49b8e59b7f2394295dbced389f
BLAKE2b-256 checksum
How to use checksums
8f6ac8d498af94691798bcb4a8b78c5aa8df00c783732f9313fc11ed76f77bf7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for collective.discussionplus 1.0b2

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page