Skip to main content

Plone content rule to create a group based on a content

Project description

Overview

Content Rules: User group actions (sc.contentrules.group) package provides content rule actions to create or remove an user group.

This package is tested with Travis CI:

Travis CI badge Coveralls badge Downloads

Use case

A college with descentralized content management and groups dedicated to research. Each group should manage its own content.

In their portal they want to host areas for each research group they sponsor. All those areas will be under the folder /research/. A research group called “Environmental Studies” will have an area at /research/environmental-studies.

Every time a new research group is added under /research/ they need to create at least two user groups:

  • Editors: Group of users responsible for publishing content and managing this area.

  • Members: Group of users with access to this area.

Also, every time a research group is removed from /research/ they want to remove existing user groups related to it.

Installation

To enable this product,on a buildout based installation:

  1. Edit your buildout.cfg and add sc.contentrules.group to the list of eggs to install

    [buildout]
    ...
    eggs =
        sc.contentrules.group

After updating the configuration you need to run the ‘’bin/buildout’’, which will take care of updating your system.

Actions

This package provides two content rules actions, one to create a new user group, other to remove an existing user group.

Create User Group

Used to create a new user group this action have three options:

Group Id

Unique name for the newly created group. You are allowed to use ${title} in here to dinamically generate the id for the group. i.e.: If this field have a value of ${title} Editors and the action is being executed for a folder with title “Environmental Studies”, Group Id will be “Environmental Studies Editors”

Group Title

Friendly name for the newly created group. You are allowed to use ${title} in here to dinamically create the id for the group. i.e.: If this field have a value of Editors for Research Group: ${title} and the action is being executed for a folder with title “Environmental Studies”, Group Title will be “Editors for Research Group: Environmental Studies”

Roles

Global roles for newly created group. Roles selected here will be effective in the whole portal.

Remove User Group

Used to remove an existing user group this action have just one option:

Group Id

Id of the group to be removed. You are allowed to use ${title} in here to dinamically generate the id for the group. i.e.: If this field have a value of ${title} Editors and the action is being executed for a folder with title “Environmental Studies”, Group Id will be “Environmental Studies Editors”

Share and Enjoy

sc.contentrules.group would not have been possible without the contribution of the following people:

  • Erico Andrei (erico at simplesconsultoria dot com dot br)

  • Héctor Velarde

  • Leonardo J. Caballero G. (leonardocaballero at gmail dot com)

Development sponsored by Simples Consultoria and IEA/USP.

Changelog

1.0b3 (2014-06-02)

  • Fix package dependencies. [hvelarde]

  • Coveralls support [ericof]

  • Implement better QA for code [ericof]

1.0b2 (2012-11-13)

  • Updated Spanish translation [macagua]

  • Update translations [ericof]

  • Fix packaging [ericof]

1.0b1 (2012-10-30)

  • Add an action to remove existing user groups [ericof]

  • PEP8 [ericof]

  • Travis support [ericof]

0.5 (2011-09-15)

  • Spanish translation [hvelarde]

  • Initial release [erico_andrei]

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

sc.contentrules.group-1.0b3.zip (37.9 kB view details)

Uploaded Source

File details

Details for the file sc.contentrules.group-1.0b3.zip.

File metadata

File hashes

Hashes for sc.contentrules.group-1.0b3.zip
Algorithm Hash digest
SHA256 0ea0c2503f5c8472ecfd5de80e4d0048eb72520cdd3838e8b1986fe58649e834
MD5 f711d68f750cb46c2ad93835d16936f8
BLAKE2b-256 b3a0b02529425687c9c7c2e52683f1bf5bd17f679dbf144e6523685df7dea0ee

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