Changes Not Applying
What This Means
This issue occurs when changes made through Steel Security do not appear to take effect on your site.
You may apply a hardening control, but the expected behavior does not change.
Common Symptoms
- protections appear enabled but have no effect
- restricted files or endpoints remain accessible
- headers do not appear after being applied
- previously visible behavior remains unchanged
Possible Causes
This issue is often caused by:
- caching (browser, server, or CDN)
- delayed server configuration updates
- conflicting rules or settings
- unsupported server environment
How to Fix It
Try the following steps:
1. Clear All Caches
- clear your browser cache
- clear any WordPress caching plugins
- purge CDN caches (if applicable)
2. Reload the Page Fully
- perform a hard refresh (e.g., Ctrl+F5 or Cmd+Shift+R)
- test in a private/incognito window
3. Check Server Environment
- confirm your server supports the applied control
- ensure configuration changes are allowed
- verify
.htaccessor server rules are being read
4. Review Conflicting Configurations
- check for overlapping rules from other plugins
- review manual server configurations
- ensure no settings override Steel Security changes
5. Allow Time for Changes
- some environments may delay configuration updates
- wait briefly and test again
What to Expect After Fixing
After resolving the issue:
- applied protections should take effect immediately
- restricted access should behave as expected
- headers or rules should appear correctly
When to Seek Help
If the issue persists:
- document the specific control applied
- note your server type (Apache, Nginx, IIS)
- check logs or error messages
- contact support with details