A limitation Limitation to specify that only users that the Users who owns all parent locations Locations of content a Content item gets a certain access right, used for content/create
permission.
Identifier | ParentOwner |
Value Class | eZ\Publish\API\Repository\Values\User\Limitation\ParentOwnerLimitation |
Type Class | eZ\Publish\Core\Limitation\ParentOwnerLimitationType |
Criterion used | n/a |
Role Limitation | no |
Possible values
Value | UI value | Description | ||
1 | "self" | Only | user which the User who is the owner of all parent | locations gets access (see "Legacy compatibility notes" #2)Locations gets access |
2 | "session" | Same as "self" (see "Legacy compatibility notes" #1) |
Legacy compatibility notes:
...
Legacy compatibility notes
- "session" ) is deprecated and works exactly like "self" in Public API since it has no knowledge of user Sessions
- User is no longer auto assumed to be owner of himself and get access create children of own user content object when
Owner
limitation is used in Public API*
...
Info | ||
---|---|---|
|
...
|
...
|
...
|
...
To make sure |
...
the User gets access to |
...
themselves when using (Parent) |
...
OwnerLimitation across 4.x and 5.x, the solution is to change the |
...
User to be the owner of |
...
their own Content item. This is accomplished using a privileged user to do the following API calls:
|