Installed Plugin. What Next? Documentation?

Also how to reset everything back to defaults??
Thanks.

Hi @ike Ten
Thanks for your suggestions, documentation is still in progress and it will be available at WP Hide & Security Enhancer

Actually setting up every option should not break anything, maybe in conjunction with certain codes. Also isolated bugs which occur on certain servers may be present, we still try to iron out those issues, so we need everyone who encounter problems to report on this forum or get in tough with me at https://www.nsp-code.com for further check.

At the moment, there isn’t a reset everything button, i’ll add this functionality in the next version or so.

Thanks

Thanks @nsp-code.
A reset button will be a great feature and save lots of work cleaning up.

[Issue] : Wappalyzer detects wordpress on your demo site. It goes further to detect W3 Total cache and even the plugin version.

A fix for W3 Total cache detection will be quite great since that plugin even rats out wordpress on Builtwith[dot]com even though built with cant detect wordpress itself.

I know I can’t demand much but only just report these bugs since even a popular commercial plugin can’t hide the dreaded W3 Total cache plugin.

Best regards.
Ike.

Below is the Wapalyzer report.
Font Script
W3 Total Cache 0.9.4.1
Cache Tool
jQuery
JavaScript Framework
WordPress
CMS
Blog
PHP
Programming Language
Nginx 1.10.0
Web Server

Actually it should hide the W3 Total Cache plugin, this is a functionality i’ve introduced since last version. Can you make sure the following are active:

1) General / Html -> Headers -> need to be Yes
2) General / Html -> Remove HTML Comments -> need to be Yes

The above will remove any trace of W3 Total Cache. You will need to clear your site cache, your browser cache and close / open the application otherwise Wapalyzer will not see any changes.

If this is not working for you can we get in touch and discuss further privately?

Thanks

Thanks you nsp-code

I set up everything except for the admin section of the plugin.
I just posted publicly so if there is a solution others will find it instead of posting a new support ticket. It works for you too in the form of less work answering routine questions.

1.New wp-login.php
Should I inculde .php extension at the end of the new wp-login
eg. example.php / log-example.ph

or should I exclude the extension
eg. example / log-example

2. New Admin Url

Should I include a forward slash [ / ] at the beginning and end of the new one?

eg /not-wp-admin/ and /not-login/

or just not-wp-admin and not-login

I know these are basic settings I should figure out myself. Am just being careful by asking since am setting the plugin up on a live website.

Thanks in advance.
Ike.

Ok figured it out.

1.New wp-login.php

Add .php extention to your new wp-login since it’s more really a new wp-login.php file than a url path.
example : new-secret-login.ph

2. New Admin Url
This is the main admin url path
example : /new-secret-login/

Thanks.
Marking as resolved