punktde/inspectorvisibility

Letzte Aktivität 15 Aug 2022 4 3380
composer require punktde/inspectorvisibility

Neos package to configure the visibility of inspector elements using privileges

0.1.3

Version
0.1.3
Type
neos-package
Release Date
Aug 15, 2022 10:07
Source
git
Distribution
zip
Requires
408e100256e78df068bf27a770be7db52174d7f9

PunktDe.InspectorVisibility

Latest Stable Version Total Downloads

This package allows you to configure the visibility of inspector elements, like properties, groups and tabs using policies. With that you can configure the visibility of these elements according to the users roles.

CAUTION: Although this is done with policies, this is not a security feature!

If you prevent a user from editing nodes, you aditionally need to define policies with an EditNodePropertyPrivilege for example.

Installation

The installation is done with composer:

composer require punktde/inspectorvisibility

Usage

The matcher can be defined using standard eel. The following properties to match for are available:

  • nodeTypeName
  • tabName
  • groupName
  • propertyName

If no policy is matching for a role, the configured visibility is used. Same, if a permission is set to ABSTAIN.

Examples

Example Policy.yaml

privilegeTargets:

  'PunktDe\InspectorVisibility\Security\Authorization\Privilege\InspectorVisibilityPrivilege':
    'PunktDe.InspectorVisibility:AdminFields':
      matcher: "${tabName == 'meta' && groupName == 'nodeInfo'}"

roles:
  'Neos.Neos:Editor':
    privileges:
      -
        privilegeTarget: 'PunktDe.InspectorVisibility:AdminFields'
        permission: DENY

Matcher Examples

  • Adress all uriPathSegment properties: matcher: "${propertyName == 'uriPathSegment'}
  • Adress all meta tabs of all nodeTypes "${tabName == 'meta'}"
  • Address all title fields of a specific type matcher: "${nodeTypeName == 'Neos.Demo:Registration' && propertyName == 'title'}"
The content of the readme is provided by Github
The same vendor provides 33 package(s).