Closed (fixed)
Project:
User Restrictions
Version:
2.1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
19 Oct 2025 at 17:30 UTC
Updated:
8 Nov 2025 at 16:39 UTC
Jump to comment: Most recent
Currently, it is not possible to decide the order used for restrictions; UserRestrictionTypeBase::matchesValue() first looks for the first restriction which allows the entered value, storing in a local variable the restriction that forbids the entered value.
UserRestrictionsListBuilder to DraggableListBuilderUserRestrictionTypeBase::matchesValue() to gather restrictions by weight (ascending order) and stop at the first matching restrictionStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
avpadernoComment #4
avpadernoComment #5
avpadernoComment #6
avpadernoThe merge request causes the following exception, when the second user restriction is created; no exception is thrown when the first user restriction is added. In the latter case, the entity.user_restriction.collection form is correctly rendered.
This is the relative backtrace.
Comment #8
avpadernoComment #11
avpaderno