delete_themes and delete_plugins caps do not obey DISALLOW_FILE_EDIT

[ryan]

Should they? Deleting is a file modification.

[ryan]

I'm leaning toward no, they shouldn't. Disallowing plugin/theme deletes seems an overloading of DISALLOW_FILE_EDIT. I can see someone setting DISALLOW_FILE_EDIT but still wanting to be able to delete plugins/themes.

[ryan]

This comes up from sites that manage everything through svn, themes and plugins included. A means of disabling theme and plugin delete links for such sites would be nice.

[ryan]

Such sites would probably need to disallow anything that touches files. Plugin/theme update, delete, install, and edit as well as core upgrades.

[ryan]

(In [14088]) Introduce DISALLOW_FILE_MOD for disabling all ops that modify core, theme, or plugins files. see #13000

[ryan]

Added DISALLOW_FILE_MODS as a super set of DISALLOW_FILE_EDIT.

[nacin]

Looks good to me.

[strider72]

Is there a comparable Role to "allow file edit"?

I would love to be able to only let one specific user do any kind of file modification....

[dd32]

I would love to be able to only let one specific user do any kind of file modification....

Thats where creating a custom role for all users, and only allowing administrators access to everything else. the custom role wouldn't include any of the update or editing related caps.