Hi,
It’s likely a configuration issue rather than the plugin failing to work.
Init Content Protector decrypts and restores the content back into your article wrapper using the CSS selector you configure in the plugin settings. By default, it uses .entry-content, but many themes use different wrappers such as .post-content, .single-content, .article-body, etc.
If the selector does not match your theme’s actual content container, the decrypted content will never be injected back into the page, so visitors will only see the skeleton placeholders.
Please check your theme’s HTML structure and set the correct “Content Selector (for JS injection)” in the plugin settings.
Example:
.entry-content.post-content.single-post-content
The plugin already exposes this setting intentionally because every theme has different markup. You can see this directly in the source code where the selector is configurable and passed into the decryption script.
Also note:
- The plugin only runs on selected post types.
- Encryption mode depends on JavaScript being enabled.
- Some aggressive cache/minify plugins may delay or break the decrypt script execution.
Once the correct selector is configured, the blog posts should display normally.
