Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

Products.PloneboardComments

Package Overview
Dependencies
Maintainers
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

Products.PloneboardComments

Tool for connecting Ploneboard to content, to make it discussable in Ploneboard forums

  • 1.0.9
  • PyPI
  • Socket score

Maintainers
1

A simple "hack" that changes Plone's built-in comment system to one that makes use of Ploneboard forums and conversations to manage comments.

It has an overrides.zcml file which overrides that standard commenting template, so as soon as Zope is restarted the standard commenting doesn't work and PloneboardComments needs to be installed via the Plone Control Panel. After installing, add a Ploneboard and Forum, and then a PloneboardComments object in the Plone root. Configure the PloneboardComments object to point to the newly created Message Board, save and then edit again and select the right forum.

PloneboardComments is "context-aware", so if you have one PloneboardComments object in the root, and another in for example /intranet/ - comments in intranet will be "ruled" by the closest PloneboardComments instance, the one in /intranet will override the one in the Plone root.

The PloneboardComments features are controlled by the "Reply to item" permission, as well as the "Discussion enabled" portal_types property, similarly to how regular Plone comments are controlled.

Note that the code that creates Conversation items in the Ploneboard Forums (in content/PloneboardComments.py) does not check whether a user actually has permission to create a Conversation item in the forum used for comments, this is considered an OK solution as a user can only create a conversation on an object they have discussion rights on.

Note: context/PloneboardComments.py has 3 translations (prefixed i18n) which aren't getting translated. So one has to manually set the Norwegian translations here if needed. Any tips on how to fix this are more than welcome.

quills_entry_macros.pt has been copied from Quills and modified (under the GPL).

For anything related to this product, contact info@nidelven-it.no.

1.0.9 (2012-10-17)

- Adding template with comment macro that can be used in listings
  (several discussable objects in one page).

1.0.8 (2012-10-17)

- Making quills integration optional (oops).

1.0.7 (2012-10-15)

- Adding copyright info for quills patch

1.0.6 (2012-10-15)

- Adding icon for PloneboardComments

1.0.4 (2012-10-12)

- Bumping for proper egg info in release

1.0.4 (2012-10-12)

 - Integrated support for Quills; Quills entries can now be
   commented on through Ploneboard forums.

1.0.3:

Eggified product.

Updated README.txt

1.0.2:

Fixed bug where non-ASCII characters would stop the creation
of conversations on an item.

Fixed bug where "comment(s)" was not tagged for translation in
template.

Reduced whitespace (newline) on translatable string in
template.

Keywords

FAQs


Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc