Example of attempting to publish a post with insecure content - classic editor.
Insecure Content Warning helps content creators with secure (HTTPS) websites avoid insecure-content warnings in the browser by flagging any elements in the content editor (such as images, videos, and embeds) that are being delivered or sourced from an insecure (HTTP) web address. All insecure elements are flagged before the content is published, and can be fixed manually or simply by clicking “fix it.”
Compatible with the “classic” editor as well as the block editor (aka Gutenberg).
Technical Notes
- Requires PHP 7.4+.
- Requires a secure / SSL (HTTPS) website, front and back end.
Usage
This plugin requires no configuration. Simply activate and the plugin will prevent posts with insecure elements from being published, as well as provide a banner with information on the offending assets.
Optional WP-CLI Commands
These are not required for normal usage of the plugin, but are available as a utility for more advanced usage.
wp icw fix
Used to fix insecure elements in existing content. Can target specific posts or bulk batches.
wp icw fix [] [--include] [--all] [--post_type] [--limit] [--offset] [--dry-run]
Example:
$ wp icw fix --all --post_type=page
Checking post content...
Total posts checked for insecure URL(s): 10
+-------------------------------------+
| URL(s) fixed summary |
+-------------------------------------+
| 0/0 URL(s) fixed in post 98 |
| 0/0 URL(s) fixed in post 96 |
| 0/0 URL(s) fixed in post 76 |
| ........................... |
| 0/0 URL(s) fixed in post 6 |
| 0/0 URL(s) fixed in post 1 |
+-------------------------------------+
Run wp help icw fix for more information on the command args.
