WP Hide & Security Enhancer Project - FAQ

Absolute None!
No files and directories are being changed on your server, everything is processed virtually! The plugin code use URL rewrite techniques and WordPress filters to apply all internal functionality and features.

There’s no requirements on php knowledge. All plugin features and functionality are applied automatically, controlled through a descriptive admin interface.

A demo instance can be found at https://demo.wp-hide.com/ or our own website WP Hide and Security Enhancer

If the server runs full-stack Nginx, the free plugin can’t generate the required format Nginx rewrite rules. It works with Apache, LiteSpeed, IIS, Nginx as a reverse proxy and compatible.

Everything works as before, no functionality is being broken. You can run updates at any time.

No, the plugin changes only assets links ( CSS, JavaScript, media files ) and not actual content URLs. There will be no negative impact from SEO perspective, whatsoever.

Yes, the plugin works with any cache plugin deployed on your site.

This free code can with Apache, IIS server types and any other set-up which rely on .htaccess usage.
For all other checks the PRO version at WP Hide PRO

There are few things to consider when run on litespeed servers:

• Ensure the liteserver actually process the .htaccess file where the rewrite data is being saved. Check with the following topic regarding this issue Post

• If you use Litespeed Cache plugin, in the Optimization Settings area, disable the CSS / JS Minify

• If your litespeed server requires to place the rewrite lines in a different file e.g. config file or interface, consider upgrading to PRO version which includes a Setup page where you can get the rewrite code WP Hide PRO.

As default, on Bitnami LAMP set-ups, the system will not process the .htaccess file, so none of the rewrites will work. You can change this behavior by updating the main config file located at /opt/bitnami/apps/APPNAME/conf/httpd-app.conf , update the line

AllowOverride None

to

AllowOverride All

Restart the Apache service through ssh

sudo /opt/bitnami/ctlscript.sh restart

More details can be found at Bitnami Default .Htaccess

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

I’m seeing this error “Unable to write custom rules to your .htaccess. Is this file writable” what does it mean?
The error appear when the plugin is not able to write to .htaccess file located in your WordPress root. You can try the followings to make a fix:

• Check if your .htaccess file is writable. This can be different from server to server, but usually require rw-rw-r– / 0664 Also ensure the file owner is the same group as php

• Sometimes the other codes wrongly use the flush_rules() which hijack the default filters for rewrite. Try to disable the other plugins and theme to figure out which ones produce the issue.

• De-activate and RE-activate the plugin, apparently worked for some users.

• Create a backup of .htaccess, then delete it from the server. Go to Settings > Permalinks > update once, this should create the file again on the WordPress root. If so, try to change any WP Hide options which will update the .htaccess content accordingly.

• There will be no harm.
• Go to admin and change some of the plugin options to see which one causes the problem. Then report it to the forum or get in touch with us to fix it.
• If you can’t log in to admin, use the Recovery Link which has been sent to your e-mail. This will reset the login to default.

• If you can’t find the recovery link or none of the above worked, delete the plugin from your wp-content/plugins directory. Then remove any lines in your .htaccess file between
  BEGIN WP Hide & Security Enhancer
  ..
  END WP Hide & Security Enhancer

• At this point, the site should run as before. If for some reason still not working, you missed something, please get in touch with us at [email protected] and we’ll fix it for you in no time!

The Recovery Link can be used to reset all plugin options and restore the site to the default state.
The link should be entered into the browser URL bar. After the operation is completed, a system message will show “The plugin options have been reset successfully”.
If the message does not show, there is a cache on your site that prevents the code to run. Locate your cache data, usually at /wp-content/cache/ and remove the files. Then re-load the recovery link.

Please get in touch with us and we’ll do our best to include it for a next version.