[Enhancement]: Add a "block edition" option for modules

[ufoloko]

Is there an existing issue for this?

• I have searched the existing issues

Description of problem

Sometimes, when some people works as admin in a site, can make some unwanted changes for a module, or even the creator of the module can make changes by mistake. So should be great to have some option to block changes for a module.

Description of solution

Should be great to have an option to "block changes" for a module. When this option is enabled, options like deletion, move, or edition can be disabled.

This is helpfull for example when you have a module used in some pages or all pages and you want to avoid unwanted changes even of your self. For example a footer html module that needs to keep untouched. If somebody needs to change, you need to disable that option, then you anybody can make changes.

Description of alternatives considered

I thing module permissions can be used to avoid this for other users, but sometimes you want to protect module changes of yourself, so this kind of functionallity can be very usefull.

Anything else?

No response

Do you plan to contribute code for this enhancement?

• Yes

Would you be interested in sponsoring this enhancement?

• Yes

Code of Conduct

• I agree to follow this project's Code of Conduct

[jeremy-farrance]

I like this idea, to improve the terminology and better express the intent, instead of "block," how about "lock"? Introducing the ability to Lock a module sounds like a really useful idea to me.

However, I can a lot of scope creep on this. I think the first version should be really specific and simple. Maybe just start by following Apple's lead with the way they lock OS settings, the lock state if very simple and just requires an extra step to unlock something before you proceed.

Example of scope creep: when someone unlocks a module and/or makes changes, the person who locked it should be notified somehow. :)

[ufoloko]

Thanks Jeremy to make this idea clear.

About the lock/unlock owner, maybe can be a good idea just who lock module can unlock, but sometimes this can be dangerous, mainly for some companies that changes people frequently, in some cases module can keep looked for some user already left company.

I think should be more simple to avoid confussion with permissions, is just a setting to avoid unwanted changes and to keep module "locked".