I’m still diggin the permissions for both users and pages.
I have a page with images and I want the “editors” to see all the cards but not allowed to delete, swap, update, change the attached image.
So far, the editor user looks like this:
and I have some specific options in the page:
But with these settings, the Editor is still being able to change the image??
Please see the screenshot below
These look like files fields, so your file permissions have no influence here? Because the user will change the page content, not the files.
That means it’s a field related permission? Is it possible to do that kind of granularity? or there any other options?
Kirby doesn’t know permissions on the field level. The only way to prevent a user from making changes to certain fields would be via programmable blueprints (and then disable those fields for certain user types), or hooks that throw an error when such fields are changed. I’d recommend the first option.
Okay, everything is set via Programmable blueprints but how do I let a specific “Editor” user to edit everyfield except these 2 but the user is still able to see the images:
Check for the user role in the PHP blueprint and then disable the field.
Yeah but if the field is disabled, the user would not be able to see the image anymore right? And this is not what we want? We just need the fields “cover” and “verso” to be uneditable but viewable.
No, a disabled field is just disabled, not hidden.
By disabled, it’s a status syntax specific to Kirby or do I use the standard?
# disabled code here
disabled is a field property: Files | Kirby CMS