Home › Forums › WordPress Plugins › Hide My WP › New Wapplyzer update now reveals WP

This topic is: resolved
Viewing 15 posts - 1 through 15 (of 17 total)
1 2
  • Author
    Posts
  • June 20, 2020 at 7:51 am #31032
    dcipher
    Post count: 66

    Hi Suman,

    The latest Wapplyzer update seems to now detect WP even with HMWP fully configured (the same config I’ve had for the past year).

    Can you please validate and confirm what changes need to be made to HMWP in order to help fix this?

    Many thanks.

    June 21, 2020 at 3:28 am #31038
    Suman M.
    Post count: 12478

    Hi, thanks for contacting us. Can you please generate debug report from HMWP start tab and post it here as private reply?

    June 21, 2020 at 5:29 am #31041
    dcipher
    Post count: 66

    Hi Suman,

    I replied privately but can’t see the reply, let me know if you’ve received it.

    June 21, 2020 at 3:21 pm #31039
    dcipher
    Post count: 66
    This reply has been marked as private.
    June 21, 2020 at 3:44 pm #31054
    Suman M.
    Post count: 12478
    This reply has been marked as private.
    June 21, 2020 at 11:16 pm #31056
    dcipher
    Post count: 66
    This reply has been marked as private.
    June 22, 2020 at 2:19 am #31062
    dcipher
    Post count: 66
    This reply has been marked as private.
    June 22, 2020 at 5:03 am #31067
    Suman M.
    Post count: 12478

    So I’ve confirmed that the reason why those assets appear with the full path is because of the LScache plugin which optimises CSS etc… without breaking site layout.
    >> LScache plugin includes the full WP path while optimizing css and hence /wp-content path visible.

    So if I disable CSS minification via the LSCache plugin, I can see that the wp-content folder in the page source is removed however wappalyzer still detects WP so I don’t think it was that that was causing it.
    >> Obviously /wp-content path visibility might lead to WP detection. It could also be that there is some other thing that makes wappalyzer detect WP. These detectors keep on updating their algorithm. So we might need to check further. Also it could be that wappalyzer has cached the previous results. So you may check after a day or so.

    June 22, 2020 at 11:24 am #31090
    dcipher
    Post count: 66

    Hi Suman,

    Thanks for your reply. So regarding your second point, definitely not a cached instance of wappalyzer as it’s been the case for a few weeks now, even before the LScache optimisations were added.

    You might have to research any algorithm changes that they may applied recently to see if HMWP needs tightening up to support proper hiding.

    June 22, 2020 at 5:53 pm #31099
    Suman M.
    Post count: 12478

    Yes, but this will take some time as I’ll need to ask our dev team to look further into this issue. Thanks!

    June 22, 2020 at 6:06 pm #31100
    Suman M.
    Post count: 12478
    This reply has been marked as private.
    June 22, 2020 at 10:27 pm #31102
    dcipher
    Post count: 66
    This reply has been marked as private.
    June 23, 2020 at 8:22 am #31112
    Suman M.
    Post count: 12478

    I could access your site now. I have assigned the issue related to WP detection via wappalyzer to our dev team. It might take some time. I’ll get back to you on this. Thanks!

    June 23, 2020 at 9:34 am #31117
    dcipher
    Post count: 66

    Brilliant, thanks Suman.

    July 19, 2020 at 11:11 pm #31498
    dcipher
    Post count: 66
    This reply has been marked as private.
  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 17 total)
1 2

You must be logged in to reply to this topic.