From iThemes Security v4.3.2, developers used get_home_path() function in place of ABSPATH to account for WordPress core in a different directory than wp-content. Since then we found that old .htaccess file generated by this plugin is not removing and generating a new .htaccess file in root directory. Since two .htaccess files one from root directory and one from wordpress own directory differing its rewrite rules, admin of the site could not able to work their sites as did before. If this is your issue, then delete .htaccess file in wordpress own directory, and don’t change any thing in the new .htaccess file in the root directory.
Thanks!
I deleted the .htaccess and still nothing. So I deleted all of the .htaccess and still I face the 404 page. Any ideas on how to proceed?
Thanks!
Hai @helpwithwp !
If you can not access your site backend, rename iThemes Security plugin folder to another name. Now you can access your site using default wordpress login url, say example.tld/wp-login.php or example.tld/wp-admn.
Note: tld/cctld means Top Leve Domain or Country Code Top level Domain.
Now you need to delete cache and deactivate any plugins installed for caching.
Revert the iThemes Security plugin folder to its actual folder name in plugins directory. Now activate iThemes Security plugin and enable feature by feature except SSL, Anyway, Hide Backend features. If every thing working as expected then get backup for both wp files and data base. Now enable hide back end feature and test if it works. If it works, then enable other plugins one by one and see which one conflict with iThemes Security. After finding the culprit for the issue, deactivate that plugin and continue for the remaining plugins.
If you still getting 404 or other issues, then you need to change or delete some date stored by iThemes security from wp-options table in your site data base. You can see about these table info here.
After solving your issues, then enable cache plugin. If still you dont get how to do all this, probably without basic knowledge of this plugin you are playing with all its features. Some tweaks of this plugin create complicated issues. I strongly suggest install wp at your local environment and test this plugin and along with other plugins. Then only do the same in production sites. But I strongly suggest don’t play with live or production sites.
