Skip to main content

hexagonit.portletroles overrides each portlets for Plone to provide different edit_view permissions to them.

Assigning different roles to those permissons happens through rolemap.xml.

Only who has permission can manage portlets through @@manage-portlets then.

Further Documentation URL

http://packages.python.org/hexagonit.portletroles/

Repository URL

https://github.com/hexagonit/hexagonit.portletroles/

Example rolemap.xml:

<?xml version="1.0"?>
<rolemap>
  <permissions>
    <permission name="Portlets: Manage portlets"
                acquire="True">
      <role name="Manager"/>
      <role name="Site Administrator"/>
      <role name="Editor" />
    </permission>
    <!-- Permission for moving and deleting portlets  -->
    <permission name="Portlets: Manage own portlets"
            acquire="True">
      <role name="Manager"/>
      <role name="Site Administrator"/>
      <role name="Editor" />
    </permission>
    <permission name="Portlets: Manage Events portlet"
                acquire="True">
      <role name="Manager"/>
      <role name="Site Administrator"/>
      <role name="Editor" />
    </permission>
    <permission name="Portlets: Manage Login portlet"
                acquire="True">
      <role name="Manager"/>
      <role name="Site Administrator"/>
    </permission>
    ...
  </permissions>
</rolemap>

With this rolemap.xml, user who has Editor role can add and manage Events portlet, but not Login portlet.

You can find which permissions are registered from overrides.zcml file in the package.

Permission for deleting and moving up/down portlets is controled by permission: Portlets: Manage own portlets.

Changelog

1.0 (2012-04-18)

  • Test for deleting and moving up/down portlet added. [taito]

0.9 (2012-03-08)

  • Code cleanups. [taito]

  • Sphinx documentation updated. [taito]

0.8 (2012-03-08)

  • Release for production use. [taito]

Contributors

  • Kai Lautaportti <kai.lautaportti at hexagonit.fi>

  • Taito Horiuchi <taito.horiuchi at hexagonit.fi>

Metadata

Release files for hexagonit.portletroles 1.0

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

Source distribution (sdist)

Source distribution for hexagonit.portletroles 1.0
File Size Uploaded Provenance
hexagonit.portletroles-1.0.zip 21.7 kB Without provenance Details

Release files / hexagonit.portletroles-1.0.zip

Download URL hexagonit.portletroles-1.0.zip
Size 21.7 kB
Tags Source
SHA-256 checksum
How to use checksums
0dc2a803f341b270af9e6c9821482bd7a4cdc2e47e035cd098991e6a8205e598
BLAKE2b-256 checksum
How to use checksums
66319c6535db4c7f3c37fae9f368f257122f5e9ea05b3528052906ccb9d8e531
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for hexagonit.portletroles 1.0

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.

Release history Release notifications | RSS feed

This release

1.0 This release

1 release file No provenance

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