One of the most common reasons of failure during the activation of the hardening options is the permissions applied to the directories or files.
Folders like “wp-content”, “wp-content/uploads”, and “wp-includes” the plugin requires to have write permissions to its in order to create a file named “.htaccess” or to append some code in it if already exists. If the plugin does not has write permissions there then the hardening will fail.
You said in this thread [1] that you are not an “expert in this stuff” but the hardening is easy to replicate by hand, try to do this… You need to use the file manager available in the control panel of your hosting account to navigate to the directory that you want to harden (in this case “wp-includes”). Then create a file named “.htaccess” or open it if already exists, and add this code [2].
Let me know how it goes.
[1] https://wordpress.org/support/topic/received-message-changes-in-the-integrity-of-your-core-files-were-detected?replies=5#post-7223721
[2] http://cixtor.com/pastio/4d75un
Thanks. It seems that the Go daddy Managed WP account, which I have , does not have a file manager. GD rep says use filezilla to access files. I have done this with something else so know it works. Just what would I create to transfer to GP? Told you I was not an expert! Thanks.
I fixed the issue with this changeset [1] which was released in version “1.7.13”, the problem was related with a new code that was introduced to support a new version of the Apache web server, the plugin was not removing the previous/old hardening rules so it entered in a conflict, this means that you will have to remove the hardening and apply it once again to fix the issue through the new code.
[1] https://plugins.trac.wordpress.org/changeset/1209852
Many thanks. Glad you found the answer. Since I have no idea of how to apply the solution, will just have to wait till an update is release. Roger
