Permisson to create a page not working

,
1

I am struggeling for days.
I have two roles: admin and editor.
The editor should not be able to create default pages.
In the blueprint/users/editor.yml I have

title: Editor

permissions:
  access:
    system: false
  site:
    update: false
  pages:
    *: true
    changeStatus: false
    delete: false
  users: false
  user:
    *: false
    changeEmail: true
    changePassword: true

in my default.yml I have

title: Default Page

options:
  create:
    editor: false

But I am still able to create pages! What am I missing?

I am listing my pages in the panel like this (site.yml):

title: Site

columns:
  - width: 1/2
    sections:
      pages:
        label: Seiten
        type: pages
        create: default

Setting create: false in the editor.yml works - then I can no more create ANY pages. Then I went to a page yml file to enable it for specific content and did this

options:
  create:
    editor: true

does not work :expressionless:

2

I just tested in a Starterkit 4.1.2, but it worked as expected. Note that you will still get the create dialog, but when submitting, you get the error message.

1 Like
3

Sorry & Thank you! I was expecting the Button to disappear.
But still, the other way around does not work.

editor.yml:

permissions:
  pages:
    *: true
    create: false

and then in my pages/termin.yml:

options:
  create:
    editor: true

I am not able to create that pages (termin), the button is missing.

4

Yes, doesn’t work that way round.

Unfortunately, the button doesn’t disappear.

Not sure what your setup is here. It would probably make more sense to hide certain templates via a PHP blueprint, where you have access to the user or something like that.

1 Like
5

Ah okay.
From the DOCS:

You can keep all permissions in the role files, but you can also overwrite them individually per page, file, user or the site in the corresponding blueprints. Those specific permission settings will always override the role settings.

Thanks for the fast help!

6

Might be a bug, after all, or the docs are wrong.