What changes
Closed to code. Open for work.
Refused while locked
Installing plugins or themes
Editing plugin and theme files
Adding code snippets
New administrators or application passwords
Still open
Posts, pages and page builders
Media and menus
Comments and non-admin users
Updates to installed plugins
Unlocking is yours
A stolen WordPress login is not enough.
Unlock from your Sitecommand dashboard with your password, for 15 or 60 minutes; the site locks again by itself. No AI client can unlock, and nothing inside WordPress can.
Lost access to Sitecommand? One line in wp-config.php turns the lock off. That file is yours on the server, out of reach of a WordPress login.
Confirm with your Sitecommand password.
Locks again by itself. Never available to an AI client.
FAQ
Questions
How is this different from DISALLOW_FILE_MODS?+
That setting stops installs, the file editors and updates for everyone, all the time, and does nothing about new administrators. Code Lock keeps updates running, also refuses new admins and application passwords, and opens for 15 or 60 minutes from your dashboard.
What if a hacker already has an admin password?+
While the site is locked, that admin still cannot install plugins, add code snippets, edit code or create new administrators. Unlocking happens only from your Sitecommand dashboard, with your password.
Will it break my page builder?+
No. Posts, pages, builder edits, media and menus stay open, and installed plugins keep updating.
What if I lose access to my dashboard?+
Add one line to wp-config.php on the site and the lock switches off. Only someone with access to the site's files can do that.
Can I see what was refused?+
Yes. Refusals are recorded and can raise an alert.
Keep reading
Related
The sites keep running.
So do you.
Connect your first site in two minutes. Free during launch.