Launch offer
20% off every Pro tier — and every renewal — for a limited time. Use the code at checkout:
Module — 18 operations
Snippets, site-wide CSS and JS, and widget, block and theme-template scaffolds — with the recovery path built before the feature.
Needs: SiteHelm Pro on a licensed site. The module ships switched off, and storing code and running code are two separate switches.
Every snippet is written inactive. Activating one runs a health check the moment it goes live — if the site stops rendering, the snippet is reverted automatically and quarantined, and an unconfirmed activation deactivates itself.
Snippets never load on SiteHelm’s own endpoint, so the channel used to remove a broken snippet keeps working even when the snippet takes the front end down. A one-request safe-mode flag skips every snippet on the way into wp-admin.
The scaffold operations return full class source as text and store nothing. Generating code and storing code are separate acts.
Where a change touches a code field, the activity log records a byte count and a digest, never the body — a snippet holding an API key stays a secret even in the audit trail.
A read still asks WordPress for a capability against the object. There is no anonymous read anywhere in the surface.
system-read
Lists the places a snippet can live — SiteHelm's own runner, always present, and any snippet plugin that is installed — and which safety guarantees each can keep
needs manage_options
system-read
Lists the stored snippets with language, hook, whether each is live and whether it is quarantined; bodies are not returned
needs manage_options
system-read
Reads one snippet in full, including its body
needs manage_options
system-read
Lists the snippets taken out of circulation because a request died while they were running, with the error that did it
needs manage_options
system-read
Fetches the home page and the login screen and reports whether each renders, breaks, or could not be reached — the same check activation runs, callable on its own
needs manage_options
system-read
Issues the one-off URL that loads the site with every snippet skipped, so the admin stays reachable while a snippet is breaking the front end
needs manage_options
system-read
Generates the source for an Elementor widget class from a description of its controls and returns it as text; nothing is stored and nothing runs
needs manage_options
system-read
Generates the source for a WordPress block — registration, attributes, render callback — as text; nothing is stored and nothing runs
needs manage_options
system-read
Generates the source for a theme template file for a post type or archive, as text; nothing is stored and nothing runs
needs manage_options
Every one of these is previewed before it runs, snapshotted before it changes anything, and verified afterwards by reading the site back. The chips are the policies the operation itself declares.
content-write
Stores one PHP snippet — always stored switched off, no argument makes it live, and refused outright if it does not lex; name WPCode or Code Snippets as the host and it is stored there instead, where only that plugin can switch it on
needs manage_options + edit_plugins re-checked
content-write
Switches one stored snippet on under the guard: health-checked immediately, auto-reverted and quarantined if the site stops rendering, and self-deactivating unless confirmed inside the window
needs manage_options + edit_plugins re-checked
content-write
Confirms that a snippet activated a moment ago should stay live — staying on is not the default, switching back off is
needs manage_options + edit_plugins re-checked
content-write
Switches one snippet off; only ever reduces what runs
needs manage_options + edit_plugins re-checked
content-write
Deletes one snippet, snapshotted first so it can be put back
needs manage_options + edit_plugins re-checked
content-write
Stores custom CSS printed on the front end — it cannot run anything, but it can make a site unusable to look at, so it is previewed and reversible like any other change; WPCode and Code Snippets can hold it instead
needs manage_options + edit_plugins re-checked
content-write
Stores custom JavaScript printed on the front end — it runs in every visitor's browser, a wider reach than PHP, and goes through the same storage discipline; WPCode and Code Snippets can hold it instead
needs manage_options + edit_plugins re-checked
content-write
Turns every snippet off at once, or back on, without knowing which one broke; the switch is read before any snippet is considered, so a broken snippet cannot defeat it
needs manage_options + edit_plugins re-checked
content-write
Puts a quarantined snippet back into circulation — through the whole activation guard again, not on trust
needs manage_options + edit_plugins re-checked
The same module described by the jobs it does, rather than by its call signatures.
featurePosts, pages, custom post types, blocks, terms and redirects — the operations an editor would otherwise perform by hand.
18 opsThe index, free and Pro.
indexWhat happens between the call and the change, on every write on this page.
reference
SiteHelm