Skip to main content

Plone Comments

Project description

Introduction

Plone Comments (quintagroup.plonecomments) is a Plone product developed to improve the site managers and editors experience with standard commenting mechanism in Plone.

Features

Plone Comments allows to:

  • Notify admin about comment posted

  • Notify commentator about his comment aproval

  • Notify author of parent comment about new follow up added

  • Moderation of comments, approval of comments

  • Anonymous commenting

  • Added Name field to comment form, it is required for anonymous comments

  • Article author can be notified about new comment after the approval by reviewer

  • List of recent comments for more comfortable moderation

Plone Comments Configlet allows:

  • Turning on/off Moderation

  • Turning on/off Manager notification

  • Turning on/off Editor notification

  • Turning on/off Anonymous Commenting

  • Configure admin e-mail for notifications

  • Configure notification subject

Plone Comments can be integrated with Plone Captchas (requires quintagroup.plonecaptchas to be installed)

Notes

Comments moderation is implemented with involvement of two stage workflow. Comments are created in “private” state and visible only to DiscussionManager group of users.

To differentiate between logged-in (registered) commentors and Anonymous commentors that pretend to be one person or other one, we use Boldness of name. The Comment author is in bold when posted by logged in member. The names provided when posting Anonymously are in plain text.

Notification subject control allows to enter custom prefix to distinct notifications coming from different sites.

Usage

One of possible UseCases:

Moderation is enabled and authors notification is turned on.

  • New comment posted in private state.

  • Notification is sent to the emails entered in Plone Comments configlet.

  • Moderator User with DiscussionManager role see the comment.

  • The comment can be deleted or published on modaration stage.

  • When comment is published notification is sent to Article Editor.

Requirements

  • Plone 3.x

  • plone.browserlayer is required for Plone 3.0.x

License

Please find license in LICENSE.GPL.

Authors

The product is developed and maintained by http://quintagroup.com team.

  • Volodymyr Cherepanyak

  • Andriy Mylenkyy

  • Mykola Kharechko

  • Vitaliy Stepanov

  • Roman Kozlovskyi

Contributors

  • Gerry Kirk: product translations improvement and proofreading

  • Dorneles Tremea: code cleanup and generic setup porting

Installation

Buildout

If you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can do this:

  • Add quintagroup.plonecomments to the list of eggs to install, e.g.:

    [buildout]
    ...
    eggs =
        ...
        quintagroup.plonecomments
  • Tell the plone.recipe.zope2instance recipe to install a ZCML slug:

    [instance]
    recipe = plone.recipe.zope2instance
    ...
    zcml =
        quintagroup.plonecomments
        quintagroup.plonecomments-overrides
  • Re-run buildout, e.g. with:

    $ ./bin/buildout
  • Restart the Zope server, for example, with the following command in the terminal:

    $ ./bin/instance restart
  • Install quintagroup.plonecomments via ZMI portal_setup. Select quintagroup.plonecomments from the list of available profiles and press Import all steps.

    Atention: If you are using a Plone version before 3.1 you need to install “plone.browserlayer”:http://pypi.python.org/pypi/plone.browserlayer (which also requires a “GenericSetup”:http://pypi.python.org/pypi/Products.GenericSetup version greater than 1.4) in your Plone site. It shows up as Local browser layer support in the Plone Add-on Products Control Panel.

Traditional Zope 2 Instance

To install quintagroup.plonecomments into the global Python environment (or a workingenv), using a traditional Zope 2 instance, you can do this:

  • Copy quintagroup folder to the /path/to/instance/lib/python directory.

  • Creare a file called quintagroup.plonecomments-configure.zcml in the /path/to/instance/etc/package-includes directory. The file should only contain this:

    <include package="quintagroup.plonecomments" file="configure.zcml" />
  • Create a file called quintagroup.plonecomments-overrides.zcml into the /path/to/instance/etc/package-includes directory. The file should only contain this:

    <include package="quintagroup.plonecomments" file="overrides.zcml" />
  • Restart the Zope server, for example, with the following command in the terminal:

    $ ./bin/zopectl restart

Uninstallation

  • To uninstall quintagroup.plonecomments - select quintagroup.plonecomments uninstall profile from the list of available profiles and press Import all steps.

Changelog

4.1.3 (2010-06-04)

  • Fixed issues #2 & #3 http://plone.org/products/plone-comments/issues [kroman0]

  • Added icon_expr for qPloneComments configlet and anchor for comments [kroman0]

  • Fixed tests, validating email & validation scripts parameters, configlet & report_abuse_template templates [kroman0]

  • Fixed AjaxReportAbuse for anonymous [kroman0]

  • Fixed email message charset in Plone4 & global variables in templates for Plone4 [kroman0]

  • Fixed InitializeClass and md5 for Plone4(python2.6) [kroman0]

  • Fixed target url for discussion_publish_comment [kroman0]

  • Fixed MailHostb secureSend call [kroman0]

  • Fixed translations and pt-br locale [kroman0]

4.1.2 (2010-01-27)

  • Fixed auto focus in commenting form [kroman0]

  • Updated the image thumb logic [mylan]

  • ‘Enable Manager moderation’ condition rolled back [kroman0]

  • Captcha removed from comment edit form [kroman0]

4.1.1 (2009-11-09)

  • Hide ‘Recent comments’ tab and ‘Enable Manager moderation’ checkbox for manager [crchemist]

4.1.0 (2009-08-11)

  • Added “report abuse” feature contributed by jcbrand. [liebster]

  • Added edit comment functionality [mylan]

  • Updated comments viewlet - now comment form present without needing to push on ‘Add comment’ button. [mylan]

4.0.1 (2009-06-05)

  • Fixed links in the email messages. [liebster]

4.0.0 (2009-04-06)

  • Plone 3.* compatibility release [liebster]

3.2.1 (unreleased)

  • Added uninstall configlet and skins

  • Converted a i18n layout to a locales layout

3.1.2 (unreleased)

  • Fixed to use the username as the comment creator. That’s necessary whenever the user is authenticated. This fixes the problems where commenters weren’t receiving any notifications. [deo]

3.1.1 (2008-09-19)

  • Fixed bug in registration of product also as a package. [liebster]

3.1.0 (2008-08-28)

  • Added pt-br translation. [erico_andrei]

  • Converted Extension/Install.py` into a complete GenericSetup profile. [deo]

  • Added note about the browser.layer dependency for Plone 3.0.x. [deo]

  • Updated tests to run with Plone 3.x. [deo]

  • General code cleanup and modernization. [deo]

  • Synchronized the discussion templates to match Plone 3.x versions. [deo]

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

quintagroup.plonecomments-4.1.3.tar.gz (61.9 kB view details)

Uploaded Source

Built Distribution

quintagroup.plonecomments-4.1.3-py2.4.egg (162.9 kB view details)

Uploaded Source

File details

Details for the file quintagroup.plonecomments-4.1.3.tar.gz.

File metadata

File hashes

Hashes for quintagroup.plonecomments-4.1.3.tar.gz
Algorithm Hash digest
SHA256 9d3be809346fd55b37bd30a42693044c512f7c3620dbf515743ceaacf6e351ce
MD5 c8cfe4b43558c1fb78940f0301eb8135
BLAKE2b-256 5afc54667c53f3c51972fb8389ebb8af307f996a0163472006fea1266f9cacaa

See more details on using hashes here.

File details

Details for the file quintagroup.plonecomments-4.1.3-py2.4.egg.

File metadata

File hashes

Hashes for quintagroup.plonecomments-4.1.3-py2.4.egg
Algorithm Hash digest
SHA256 4bee7931b7431cec9edcd52116533604892c1931b05663163dded66034291311
MD5 c69024cd6d64d23f9eef5a68d4316196
BLAKE2b-256 d755e5f45859a2a2a6538c7b70e87d9f0cae4d1728f12b271062778853a7dd98

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page