Sobol Safe Save

Description

WordPress quietly removes HTML that the person saving is not allowed to publish. No warning, no
notice, no record: the editor closes, the content looks wrong, and nobody knows why.

It happens more often than most people realise, because it has nothing to do with the content and
everything to do with who saved it. Anyone without the unfiltered_html capability is affected —
that is every Author and Contributor on a normal site, and every user except the super admin on
multisite, site administrators included.

Sobol Safe Save tells you before it happens.

What it does

• Checks your content while you write, a moment after you stop typing.
• Warns you before you save that this save will change your content.
• Lists which blocks are affected, and takes you to them.
• Says what will go: a removed <iframe>, an onclick attribute, a mask-image style, a block
  marker that will be rewritten.
• Works in the block editor.
• Never blocks a save. It is a warning, not a gate. You stay in control of your own content.

How it knows

Sobol Safe Save does not guess, and it does not keep its own list of what WordPress allows. It runs your
content through the same code WordPress itself runs on save — including the filters that are not
KSES at all, such as the one that rewrites certain characters and the one that trims post titles —
and reports the difference. Its test suite checks the prediction against what actually lands in the
database, on every WordPress version it supports.

What it does not do

Nothing is sent anywhere. There is no tracking, no external service and no account. The analysis
happens on your own server, and nothing is stored.

For developers

Sobol Safe Save exposes documented PHP hooks and a JavaScript data store so that an add-on can build on
it — an audit log, alerts, per-role policies. See the extension documentation.

Development source

The human-readable JavaScript/TypeScript source and build tools for the editor assets are available in
the public plugin source.

To rebuild the editor assets, install the dependencies in that directory and run npm run build.

Technical details