Forum Replies Created
Ok so i appears as though this happens if you use a plugin such as LScache which has the ability to HTTP/2 server push CSS and JS assets.
It uses the full path of the asset instead of it honouring HMWP.
Do you have any comments or recommendations around this?
I tried that previously and it caused issues with certain functions of the site so I had to revert.
I can say that prior to version 6 of the plugin, this all worked fine, I had the exact same configuration as I do now and wappalyzer was not detecting WP.
Thanks for the reply Suman.
I’ll keep this disabled for the time being however one thing I did notice was that when this feature was enabled, Wappalyzer could not detect the site as WP.
I know there’s another ‘Full Hide’ feature however this causes problems with wp-admin loading of external plugin content.
Either way, it would be great to improve this feature for a future release.
Thanks for the reply. Disabling that option removed the console errors however I suspect that it might be something to do with compatibility issues between that HMWP feature and the Translatepress plugin that we use for multi-lingual requirements.
The auto.js console error would only appear when selecting a language other than the site default being English. Any other language would then see this error appear. If this is in fact a question of compatibility with HMWP, could you possibly take a look at helping with a resolution?
Many thanks in advance.
Great, appreciate the quick reply!