Compatibility and Plugin Conflicts

Known Compatibility Notes

• Wordfence — compatible. Both can run simultaneously. WP 1 Click LockDown covers hardening; Wordfence adds firewall and malware scanning. No conflicts.
• iThemes Security / Solid Security — compatible, but both plugins cover some of the same settings. If you run both, disable duplicate features in one of them to avoid conflicts.
• WooCommerce — fully compatible. Customer login and checkout are separate from /wp-login.php and are unaffected by login URL masking.
• Jetpack — see our dedicated Jetpack and XML-RPC guide if Jetpack stops working after disabling XML-RPC.
• Elementor / page builders — no conflicts. WP 1 Click LockDown does not modify front-end rendering.
• Caching plugins (WP Super Cache, W3 Total Cache, WP Rocket) — compatible. If your custom login URL is cached, add it to your caching plugin's exclusion list.
• Cloudflare — fully compatible. The plugin reads CF-Connecting-IP for accurate IP detection behind Cloudflare.

How to Diagnose a Conflict

1. Identify when the issue started — was it immediately after installing WP 1 Click LockDown?
2. Temporarily disable WP 1 Click LockDown (deactivate the plugin).
3. Test whether the issue resolves. If yes, a conflict exists.
4. Re-activate WP 1 Click LockDown and disable individual settings one by one to identify the specific feature causing the conflict.
5. The most common culprits are: custom login URL, XML-RPC disabling, and REST endpoint blocking.

Reporting a Conflict

If you identify a conflict that this guide does not cover, please report it to our support team at wp1clicklockdown.com/contact with: the name and version of the conflicting plugin, the WP 1 Click LockDown setting that causes the conflict, and any error messages or unexpected behaviour you observe.