bacbos / bolt-menu-editor

a visual menu-editor extension for the awesome bolt cms
Other
21 stars 23 forks source link

Settings access permissions for users #72

Closed Infusednl closed 6 years ago

Infusednl commented 6 years ago

Hi SahAssar,

First off, thanks for your great plugin, I really appreciate the hard work you've put in it.

I read your documentation but I just can't figure out how to give my clients access to your plugin so they can edit their menus themselves. I tried editing the permissions file in various ways but without any luck.

Could you provide an example of how to edit the permissions.yml file so other user roles can see and edit the menu?

SvanteRichter commented 6 years ago

Hi @Infusednl,

It uses the parameter set in the config, see here: https://github.com/bacbos/bolt-menu-editor/blob/master/config/config.yml.dist#L47

That is then matched based on the role with the main bolt permissions yml file.

Did make it clearer? I can fix up an example if not.

sbonardt commented 6 years ago

Hi,

I ran into this as well, trying to get custom permissions in.

If you want custom permissions you will have to:

Default the menu permissions us the same permissions setting that is specified for "file:config" So if you only edit the general Bolt permissions.yml and for instance add the following to the global permissions:

menueditor: [ editor ]

That would not work.

This because the setting in /app/config/extensions/menueditor.bacboslab.yml file still says to look at the "files:config" line in permissions.yml in stead of your custom menueditor line.

SOLUTION: So also change the /app/config/extensions/menueditor.bacboslab.yml file, and set the permission to check the 'menueditor' permission line in permissions.yml (or whatever you called it)

# Permission for the menu editor
# Use an existing permission from the /bolt/roles page, or create your own
permission: menueditor
SvanteRichter commented 6 years ago

Closing this, since the permission to edit the menu file in bolt is set to "file:config" so we use the same. Doing this right would probably require more granular permissions in bolt.