Init Content Protector – Anti-Copy, Anti-Scrape, Encrypt-All
| 开发者 | brokensmile.2103 |
|---|---|
| 更新时间 | 2025年8月16日 15:11 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.8 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Init Content Protector is a powerful yet lightweight plugin that safeguards your post content from unauthorized copying, scraping tools, and inspection via browser developer tools.
This plugin is part of the Init Plugin Suite — a collection of minimalist, fast, and developer-focused tools for WordPress.
GitHub repository: https://github.com/brokensmile2103/init-content-protector
Features:
- JavaScript-based copy protection (blocks selection, right-click, print, DevTools access)
- Full content encryption with client-side decryption using CryptoJS
- Keyword cloaking using CSS pseudo-elements
- Invisible noise injection to confuse crawlers
- Per-post type configuration
- Custom encryption key per site
- Custom content selector support Use this plugin to harden your site's content visibility while maintaining a smooth reading experience for real users.
安装:
- Upload the plugin files to the
/wp-content/plugins/init-content-protectordirectory, or install via the WordPress plugin screen. - Activate the plugin through the 'Plugins' menu in WordPress.
- Go to Settings → Init Content Protector and configure your preferred options.
常见问题:
Will this affect SEO?
If you enable full content encryption, search engines will not be able to see the content. Only use this option if SEO visibility is not required.
Does this plugin support custom post types?
Yes. You can choose which post types are protected in the settings page.
Can I use my own encryption key?
Yes. You can set a custom key per site for added security.
更新日志:
1.1 – August 16, 2025
- Changed minimum WordPress requirement to 5.7 to leverage wp_get_inline_script_tag for safer inline script output
- Replaced wp_add_inline_script with direct inline injection for guaranteed execution across all single post pages
- Added inline script nonce/type support via wp_get_inline_script_tag for enhanced security
- Ensured encrypted payload is always available early in content, even if certain script handles are missing
- Added CustomEvent trigger (init-content-payload-ready) to allow frontend scripts to react when encrypted content is ready
- Prevented duplicate inline script injection when content filters run multiple times
- Initial release
- JavaScript-based content protection (block copy, right-click, print, DevTools)
- Full AES-256 content encryption with CryptoJS decryption
- Invisible keyword cloaking via ::before and randomized CSS class
- Random noise injection (hidden spans) to confuse crawlers
- Supports multiple post types (customizable)
- Custom encryption key per site
- Custom content selector for JS targeting
- Fallback styling compatible with light/dark themes
- Modular settings page with sanitize and validation