collective-folderprotection 2.3

No project description provided

Contents

• Introduction

• Installation

• Usage

• Password protection

  • Through the add/edit views

  • Through the “Assign password” view

  • Programatically on content creation

• Delete protection

• Rename protection

• Changelog

  • 2.3 (2021-01-11)

  • 2.2 (2021-01-06)

  • 2.1 (2019-12-10)

  • 2.0.1 (2019-08-06)

  • 2.0 (2019-08-06)

  • 1.0-dev (unreleased)

Introduction

This package provides 3 behaviors to secure your Dexterity content types in 3 ways:

• “Password Protected”: Will allow you to set a password to specific object so any user, except manager or its owner, needs to provide it to access it or its children (if the protected content type is a folderish)

• “Delete Protection”: Intended for folderish content types, this behavior will protect the content’s children for being removed.

• “Rename Protection”: Intended for folderish content types, this behavior will protect the content’s children for being renamed. Note: For this particular behavior, this only protects renaming through the UI, and does not protect the object if it is renamed using manage_renameObjects programatically from its parent.

Installation

Just add ‘collective_folderprotection’ to your eggs list in your buildout and re-run buildout. The dexterity is included by the use of the ‘dexterity’ extra, so make sure to include that, or to pull dexterity separatedly.

Usage

After installing this product, you should be provided with 3 new behaviors to activate from the “Dexterity content types” tool. If you want to enable them from your type XML, just add any of the following:

• collective_folderprotection.behaviors.interfaces.IPasswordProtected

• collective_folderprotection.behaviors.interfaces.IDeleteProtected

• collective_folderprotection.behaviors.interfaces.IRenameProtected

Password protection

There are 3 different ways in which you can assign a password to your “Password protected” enabled content.

Through the add/edit views

When adding or editing a content type which has the behavior enabled, you should see a new field along the schema, with the “Password” label. Enter your password here to assign it. Leave it blank, to remove password protection for this specific object. NOTE: This is not available for Archetypes.

Through the “Assign password” view

You should see a new tab for an object which has the behavior enabled. Going to this view and entering any password will assign it. Leave it blank, to remove password protection for this specific object. This view is independent from the add/edit ones, you can use either one.

Programatically on content creation

If you are creating content programatically, you can assign a password when calling the function, just by adding the optional “password” argumnent.

from plone.dexterity.utils import createContentInContainer
...
...
createContentInContainer(self.portal, "your.app.dexterity.fti.information", title=title, password=pw)

Delete protection

When the behavior is enabled for a given content type, a new checkbox will be shown in both the add and the edit screens, when creating or editing that specific content type. Marking the checkbox will protect this element and its direct children (if this is a folderish type) from being deleted.

Rename protection

When the behavior is enabled for a given content type, a new checkbox will be shown in both the add and the edit screens, when creating or editing that specific content type. Marking the checkbox will protect this element and its direct children (if this is a folderish type) from being renamed. Contributors ============

• Franco Pellegrini, Original Author

Lock Icons provided by http://www.danilodemarco.com/

Changelog

2.3 (2021-01-11)

• Bugfix: Infinite loop when context is the actual Plone site [frapell]

2.2 (2021-01-06)

• Remove the password protection field from the edit and add forms, to avoid issues with browsers password auto-fill causing issues [frapell]

• Create a new password widget to use the autocomplete attribute in the <input> field, to prevent browser auto filling passwords [frapell]

• Replace the checkbox to clear password protection with a clear red button [frapell]

• Include a viewlet that will show up when the given folder or a parent folder is password protected [frapell]

• Include a richtext field to provide the ability to include a reason on why the folder is password protected [frapell]

2.1 (2019-12-10)

• Raise exceptions if a protected item is renamed or deleted [frapell]

• Include uninstall profile and add post_install routines to ignore exceptions [frapell]

2.0.1 (2019-08-06)

• Fix rst format for pkg description [frapell]

2.0 (2019-08-06)

• As of this version, this product only supports Plone 5.0+

• Remove support for Archetypes [enfold-josh]

• Support Python 3 and Plone 5.2 [enfold-josh,frapell]

• Catch exception raised when inserting post_traverse hook during a non-publishing traversal. [enfold-josh]

• Fix tests. [enfold-josh]

• Change functional test files extensions to .robot [enfold-josh]

1.0-dev (unreleased)

• Add support for Archetypes [frapell]

• Make Dexterity an optional dependency [frapell]

• Include behavior to prevent removing items from a folderish [frapell]

• Include behavior to prevent renaming items in a folderish (only through UI). [frapell]

• Include behavior to allow setting a password for viewing a folder [frapell]

• Package created using templer [frapell]