WP Hide & Security Enhancer

Yes—100% beginner-friendly.
You don’t need to write a single line of PHP to customize or manage this plugin. Every feature is controlled via a clear, intuitive admin panel with descriptive labels, tooltips, and contextual help. Whether you want to hide common WordPress paths, rename your wp-content folder, or inject security headers, each option can be toggled on or off with a simple click. If you ever get stuck, hover over the question-mark icons for guidance, or check out our step-by-step documentation.

Yes, you can check out a live demo at https://demo.wp-hide.com/. Additionally, you can visit our official website, WP Hide and Security Enhancer, for more information.

Free Version: Does not auto generate native Nginx rewrite directives. However, you can still run it behind an Nginx reverse proxy or on hybrid setups (e.g., Apache + Nginx). However, it is fully compatible with Apache, LiteSpeed, IIS, and Nginx when used as a reverse proxy.
For Nginx conside WP Hide PRO.

WP Hide PRO: Includes a dedicated UI for generating Nginx configuration snippets—simply paste them into your server block to enable full URL masking, asset renaming, and security header rules. For more details, check out WP Hide PRO.

Yes, updates remain effortless.
Our plugin is designed to play nicely with the WordPress update process. You can upgrade your core, themes, and all other plugins through the dashboard or via WP-CLI without disabling WP Hide. All rewrite rules and filters persist through updates, so there’s no downtime or extra steps required.

Not in the slightest.
We only rewrite the paths to static assets (CSS, JS, images) and administrative URLs—your publicly visible content URLs (posts, pages, categories) remain unchanged. Search engines will continue to index your site normally, and any existing sitemaps or canonical tags will work exactly as before. In fact, by hiding version parameters and generic WordPress identifiers, you may see a slight improvement in perceived site quality.

Fully compatible.
Whether you’re using WP Super Cache, W3 Total Cache, LiteSpeed Cache, or any other popular caching layer, WP Hide integrates without conflict. All rewritten URLs are cached just like your standard assets. If you enable HTML, CSS, or JS minification in your cache plugin, WP Hide will automatically adjust to serve the correct file paths.

Critical defenses, made easy.
HTTP Security Headers (like Content Security Policy, X-Frame-Options, and Strict-Transport-Security) instruct browsers to apply extra safeguards when serving your site. Normally, you’d have to edit .htaccess or web server config files—now you can add, customize, and test these headers directly from a graphical interface. No manual coding, no syntax headaches; just point and click level security hardening.

Out of the box:
• Apache (with .htaccess support)
• IIS (web.config)
• Any server behind Nginx, Varnish, or HAProxy

For other environments:
Consider upgrading to WP Hide PRO, which provides tailored configuration snippets and an enhanced Setup page for Nginx, OpenLiteSpeed, and more.

1. Enable .htaccess Processing
   Make sure your OpenLiteSpeed instance is configured to read .htaccess files—see this support thread for guidance.
2. Adjust Cache Plugin Settings
   If you use LiteSpeed Cache, turn off the CSS/JS Minify option (under Optimization Settings) to prevent conflicts with WP Hide’s rewrite rules.
3. Custom Config File
   If your server requires rules outside of .htaccess (e.g., in httpd-config.conf), WP Hide PRO can generate the exact rewrite blocks you need—no guesswork involved. See WP Hide PRO details.

By default, Bitnami LAMP setups do not process .htaccess files, so rewrites won’t work. To resolve this:

• Update the main config file located at /opt/bitnami/apps/APPNAME/conf/httpd-app.conf.

  AllowOverride None

to

AllowOverride All 

• Restart the Apache service through SSH:

  sudo /opt/bitnami/ctlscript.sh restart

For more details, refer to the Bitnami documentation.

You can still keep the configuration as it is using the WP Hide PRO, more details at Setup the plugin on Bitnami WordPress LAMP stack

If you see the error “Unable to write custom rules to your .htaccess. Is this file writable?”, follow these steps:

1. Verify File Permissions. Ensure .htaccess has permissions 0664 (rw-rw-r–) or 0644, owned by the same user/group running PHP.
2. Check for Conflicts. Temporarily disable other plugins or themes that may lock or rewrite .htaccess. Reactivate them one by one to isolate the conflict.
3. Reinitialize the Plugin. Deactivate and then reactivate WP Hide; this often resets internal flags and allows writing.
4. Regenerate .htaccess. Backup and delete your existing .htaccess, then visit Settings → Permalinks to rebuild it. Afterward, return to WP Hide settings to reapply your custom rules.

Don’t worry—your site will not be harmed. Here’s how to troubleshoot:

• Log in to your admin dashboard and adjust plugin settings to identify the issue. Report the problem on our forum or contact us for assistance.

• If you can’t access the admin area, use the Recovery Link sent to your email to reset the login to default.

• If the Recovery Link doesn’t work or you can’t find it, delete the plugin from the wp-content/plugins directory and remove any lines in your .htaccess file between:
  BEGIN WP Hide & Security Enhancer
  ..
  END WP Hide & Security Enhancer

  • Your site should now function as before. If issues persist, contact us at [email protected], and we’ll help you resolve it quickly.

The Recovery Link resets all plugin options and restores your site to its default state. To use it:

• Enter the link into your browser’s URL bar.

• After the process completes, you’ll see a message: “The plugin options have been reset successfully.”

• If the message doesn’t appear, clear your site’s cache (usually located in /wp-content/cache/) and reload the Recovery Link.

We’re continuously improving WP Hide! If there’s a feature you need—whether it’s a new rewrite rule type, custom header option, or integration with third party plugins—please contact us. Your suggestions drive our roadmap, and we’ll do our best to include it in an upcoming release.