| 开发者 | lsobolew |
|---|---|
| 更新时间 | 2026年9月28日 18:20 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
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
<iframe>, an onclick attribute, a mask-image style, a block
marker that will be rewritten.npm run build.
Most likely nothing of yours is being filtered. On a single site, administrators and editors hold
the unfiltered_html capability, so WordPress leaves their content alone and Sobol Safe Save has nothing
to report. Try the same content as an Author.
No. It warns you before you save, and the save button works exactly as it did. What you do about the warning is up to you.
No. Sobol Safe Save only ever reads. The changes it reports are made by WordPress itself, and would happen whether or not this plugin is installed — the difference is that you now know about them.
The check runs on your own server a short pause after you stop typing, never on every keystroke, and it stops asking altogether for users whose content is not filtered. The delay is configurable.
Yes, and that is where it matters most: on multisite only the super admin may post unfiltered HTML, so a site's own administrator loses content exactly as an author does.
Not yet. This version covers the block editor only. Classic editor support is written and works, but it is not shipped until it has the same end-to-end test coverage as everything else here.