Restore Additional CSS and editor features

AutoShield’s Restrict risky post content policy can hide Additional CSS or limit editor features that require unfiltered HTML.

Check developer requirements

Sites using advanced editors, embeds or scripts may need these features. Review the requirement before enabling the restriction for those clients.

Allow the features on one site

1. Exclude that installation from AutoShield.
2. Select it in WordPress Management.
3. Open Choose action → WP-AutoShield → Hardening → Enable scripts in posts and review the selected site before confirming.

Choose Enable scripts in posts only for the site’s verified editor requirement. This is separate from enabling dashboard file editing. Select the image to view it full size; use your browser’s Back command to return.

4. Reopen the editor and check the feature you needed.

For a server-wide policy change, turn Restrict risky post content off in WordPress Settings, then apply the explicit action to sites that already have the restriction.

Restrict risky post content controls unfiltered HTML capabilities. It is separate from dashboard plugin/theme file editing. Select the image to view it full size; use your browser’s Back command to return.

Allow only what the site needs

Permitting unfiltered HTML also permits risky embeds and scripts. Keep the restriction for sites that do not need those capabilities. Dashboard plugin/theme file editing is a separate control.