Support » Plugin: Sucuri Security - Auditing, Malware Scanner and Security Hardening » Changin wp-content to to custom one, Sucuri Scanner could not find its path

  • Resolved *B.V.RammannaRaau*

    (@reviewkeys)


    We have been testing and working with this plugin. “Restrict wp-content access” under “Hardening” option not working as expected. If wp-content directory changed to customized directory name, then Sucuri Scanner could not find this changed directory. So, it says “WP-content directory not hardened”. But it works as expected if wp-content directory not changed to something other. It’s a minor issue that this plugin failed to find absolute path to wp-content directory.

    https://wordpress.org/plugins/sucuri-scanner/

Viewing 1 replies (of 1 total)
  • Plugin Author yorman

    (@yorman)

    I fixed this here 978150, the new code will be available in the next version of the plugin 1.6.9, this update includes new options in the Settings and I recommend to go and check them.

Viewing 1 replies (of 1 total)
  • The topic ‘Changin wp-content to to custom one, Sucuri Scanner could not find its path’ is closed to new replies.