We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
extends
git clone [email protected]:getkirby/starterkit.git cd starterkit composer install php -S localhost:3001 kirby/router.php
site/blueprints/users/base.yml
fields: foo: type: text permissions: users: create: false delete: false update: false access: settings: false users: false
site/blueprints/users/editor.yml
extends: users/base title: editor
login with an editor user and go to http://localhost:3001/panel/users
users.create: false
you can still edit other users fields, although: users.update: false
users.update: false
if you put the permissions in site/blueprints/users/editor.yml directly:
title: editor permissions: users: create: false delete: false update: false access: settings: false users: false
Everything works as expected.
conclusion:
with extends fields are inherited, but permissions are not. This is unexpected, since all other blueprints can be orchestrated in this manner.
kirby: 4.0.3 and 3.10.0 php: 8.2.13
4.0.3
3.10.0
8.2.13
The text was updated successfully, but these errors were encountered:
No branches or pull requests
To reproduce
site/blueprints/users/base.yml
:site/blueprints/users/editor.yml
:login with an editor user and go to http://localhost:3001/panel/users
users.create: false
you can still edit other users fields, although:
users.update: false
if you put the permissions in
site/blueprints/users/editor.yml
directly:Everything works as expected.
conclusion:
with
extends
fields are inherited, but permissions are not.This is unexpected, since all other blueprints can be orchestrated in this manner.
Your setup
kirby:
4.0.3
and3.10.0
php:
8.2.13
The text was updated successfully, but these errors were encountered: