BlockingLimitation

Available on version 5.3.2 and higher

A generic limitation type for use when no implementation has been made o= f a limitation, and it needs to be configured to avoid LimitationNotFoundEx= ception.
It is called blocking as it will always tell permissions system= user does not have access on any policy it is assigned to, making permissi= on system move on to next policy.

Id= entifier	`n/a (configured for ezjscore limitation FunctionList out of the box)`
Va= lue Class	`eZ\Publish\API\Repository\Values\User\Limi= tation\BlockingLimitation`
Type Class	`eZ\Publish\Core\Limitation\B= lockingLimitationType`
Criterion used	MatchNone
Role Limitation	no

Possible values

Value	UI value	Description
`<mixed>`	`<mixed>`	This is a generic limitations which does not = validate the values provided to it, make sure to validate the values passed= to this limitation in own logic.

Configuration

As this is a generic limitation you can configure your custom limitation= s to use it, out of the box FunctionList is using it in the following way:<= /p>

=20

    # FunctionList is a ezjscore limitations, it only applies to ez=
jscore policies not used by
    # API/platform stack so configuring to use "blocking" limitation to avo=
id LimitationNotFoundException
    ezpublish.api.role.limitation_type.function_list:
        class: %ezpublish.api.role.limitation_type.blocking.class%
        arguments: ['FunctionList']
        tags:
            - {name: ezpublish.limitationType, alias: FunctionList}

= =20