On This Page
On This Page
Disable File Editing
Overview
Removes the Theme Editor and/or Plugin Editor from wp-admin so compromised accounts cannot rewrite code from the browser. Both editors default to blocked. When both are blocked, sets DISALLOW_FILE_EDIT and blocks direct editor access (including admin-ajax paths). Does not stop FTP/SSH/host file managers. Soft overlap with code-snippet / config editors (different surfaces).

- Production hardening baselines
- Client sites where Theme Editor is a liability
- Shared-admin environments
Features
Theme and/or plugin editor off
DISALLOW_FILE_EDIT
Capability / direct-access block
Reversible
Use Cases
- Client production sitesRemove Theme/Plugin Editor before handoff.
- Multi-admin teamsStop “quick CSS edits” that become untracked production changes.
- Incident surface reductionPair with 2FA and Activity Log for privileged-access hygiene.
Frequently Asked Questions
What does Disable File Editing do in WP PowerSuite?
It removes the dashboard screens that let anyone edit theme or plugin code from the browser.
How do I enable Disable File Editing in WP PowerSuite?
Enable the module and keep theme and/or plugin editor toggles blocked (both default on).
Who should use Disable File Editing?
Anyone hardening production WordPress against browser-based code edits.
Can I still edit files via SFTP?
Yes. This only removes the wp-admin Theme/Plugin Editors.
Is Disable File Editing a free or Pro module in WP PowerSuite?
It is included (free) with WP PowerSuite.

