Home › Forums › WordPress Plugins › Hide My WP › Website page source still not covered
- This topic has 9 replies, 2 voices, and was last updated 8 years, 12 months ago by
envatoshadi.
-
AuthorPosts
-
November 17, 2016 at 7:09 am #12908
Hello and hope you are doing good,
Unfortunately all of our page sources code still not covered/hidden and any one easily can read the source code to find the details like plugins and other directories .. We have a firefox and we run CTL+U , even with HTML detectors such : (http://www.submitexpress.com/page-snooper.html) and (http://tools.seochat.com/tools/html-source-viewer/)
Could you please advise on this issue .. Thank you ..
November 17, 2016 at 7:10 am #12909This reply has been marked as private.November 18, 2016 at 4:50 am #12931Hi, can you please let us know the URLs and text in the page source that you are talking about? Also, let us know your website’s wp-admin login details (as private reply), so that we can look into the issue further.
November 18, 2016 at 7:57 am #12943This reply has been marked as private.November 18, 2016 at 9:20 am #12946Wappalyzer: We are already working on an update that shall handle wappalyzer detecting wordpress and plugins. The new version will be out in few weeks.
HMWP won’t replace/mask the plugin/theme names deep down in the path.
For example: HMWP will convert http://www.yourdomain.com/wp-content/plugins/some-plugin/assets/inc/some-plugin/some-plugin.js to something like http://www.yourdomain.com/ext/a23hge/assets/inc/some-plugin/some-plugin.jsIn above example, the plugin name “some-plugin” deep in the path is not replaced. In such case you’ll need to add replacement in “replace urls” option like below:
wp-content/plugins/some-plugin/assets/inc/some-plugin/some-plugin.js ==> xyz.js
For more info regarding the replacements:
https://codecanyon.net/item/hide-my-wp-amazing-security-plugin-for-wordpress/4177158/faqs/20827November 19, 2016 at 11:40 pm #12967Hello Suman ,
Thank you for your reply .. that was useful .. 🙂November 19, 2016 at 11:48 pm #12968Hello,
We are not sure were we got wrong or missed some settings .. because after we installed the W3 we became detectable to most WP detectors websites ..Please Could you advise on this ..
November 19, 2016 at 11:50 pm #12969This reply has been marked as private.November 20, 2016 at 1:14 pm #12990This reply has been marked as private.November 22, 2016 at 6:44 am #13009Hello Suman ,
Thank you for your reply .. Its a great plugins .. all the best .. -
AuthorPosts
You must be logged in to reply to this topic.

