Skip to main content

Modified policy for deleting objects in Plone

Project description

Introduction

Change some parts of Plone and make possible for users to delete contents not so easily.

The Plone behaviour

Plone (Zope) base the power to delete object looking for the “Delete objects” permission on containers. This mean that normally users that can delete contents inside a folder can delete all contents. In our experience, no-one want a workflow that make possibile to users that can’t modify a content, to be able to delete it.

This product change the Plone user interface behaviour, hiding the possibility to delete contents when you can’t modify it.

How Plone works after the installation

For deleting a content you must have:

  • Delete objects” permission on the parent folder

  • Delete objects” permission on the content itself

  • Beeing able to modify the content (all the contents) you want to delete

Security

This product is mainly targeted on Plone UI and it monkeypatch the low level permission for cutting documents.

If you run a task, a 3rd party product or whatever piece of code that delete objects, this will run with the default Plone permissions (so, only checking the “Delete objects” on containers).

Alternatives

A very similar product (probably better maintained): collective.deletepermission

Authors

This product was developed by RedTurtle Technology team.

RedTurtle Technology Site

Changelog

2.2.0 (2020-03-06)

  • Conditionally patch BaseBTreeFolder. This give some issues running tests [keul]

  • Fix imports for python3 compatibility [cekk]

2.1.1 (2013-12-16)

  • Do not handle manage_pasteObjects anymore. It is a good fix for Plone, but this was the wrong product (we only care about deletion here) [keul]

2.1.0 (Unreleased)

  • Fixed low level Archetypes permissions for manage_cutObjects and manage_pasteObjects [fdelia]

2.0.0 (Unreleased)

  • Plone 4.1 compatibility [fdelia]

1.1.0 (2010-12-06)

1.0.5 (2010-07-17)

  • added z3c.autoinclude [keul]

1.0.4 (2010-06-03)

  • customized the script of cut from folder_contents. Now performs the check that the user can modify the objects who wants to cut. [mirco]

1.0.3 (2010-04-15)

  • Release on RedTurtle pypi

1.0.2

  • Cleaned the egg format

1.0.1

  • Bug fixed: the delete object menu voice was always available.

  • Added policy for cut menu voice, like the delete ones you can cut only if you can modify.

1.0.0 - Unreleased

  • Initial release

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

redturtle.deletepolicy-2.2.0.tar.gz (14.4 kB view details)

Uploaded Source

File details

Details for the file redturtle.deletepolicy-2.2.0.tar.gz.

File metadata

  • Download URL: redturtle.deletepolicy-2.2.0.tar.gz
  • Upload date:
  • Size: 14.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.17

File hashes

Hashes for redturtle.deletepolicy-2.2.0.tar.gz
Algorithm Hash digest
SHA256 8945bc527a7df2d55108f0ab1b1e0fafaf6a5f4bd98015ec93c1ddc8de3f7ca4
MD5 7631fe139da671ceac715a7160148539
BLAKE2b-256 8394403f9c2af364d3b21466a2add043e2ddbe5ee61bdf8062e9387fca3dc375

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