#16462 closed enhancement (wontfix)
Plugin Editor does not work for Must-Use Plugins
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.1 |
Component: | Plugins | Keywords: | |
Focuses: | Cc: |
Description
Since [10737] (WP 2.8), WordPress has support for so called Must-Use Plugins. Since [13233] (WP 3.0) those are listed in the admin panel.
By default, Plugins can be edited on the Edit Plugins page (/wp-admin/plugin-editor.php
).
On WordPress 3.0.4 it's not possible to edit Must-Use plugins.
User who can edit plugins should be enabled to edit the must-use-variant of plugins as well.
Related: #11861
Change History (4)
#3
follow-up:
↓ 4
@
11 years ago
If WordPress core is going to "allow" users to edit Plugins on-the-fly, why should core differentiate between must-use Plugins and Plugins that can be deactivated? This differentiation makes no sense, unless the editor could only be used to edit deactivated Plugins.
If WordPress core provides a user capability specific to editing Plugins, then that capability should apply to all Plugins.
#4
in reply to:
↑ 3
@
11 years ago
Replying to chipbennett:
If WordPress core is going to "allow" users to edit Plugins on-the-fly, why should core differentiate between must-use Plugins and Plugins that can be deactivated? This differentiation makes no sense, unless the editor could only be used to edit deactivated Plugins.
If WordPress core provides a user capability specific to editing Plugins, then that capability should apply to all Plugins.
I think the way it works right now is the smarter route.
Normal plugins will automatically be deactivated if a fatal error is detected, whereas "must-use" plugins can't be deactivated, error or not. I definitely wouldn't want to be in a situation where it would be possible to introduce a fatal error into a plugin via the interface that can't be deactivated from that same interface.
Should we be allowing users to edit must use plugins? I think this is intentional.