Did you ever find a fix for this? I have yet to be able to find one. Thanks.
Hi, not yet, waiting for my partner (he´s the mysql specialist) developing the right sql commands…but we are too busy at the moment. Sorry…
No problem. Thanks. I temporarily went back to wp-content by changing the wp-config file back accordingly. This resolved 99% of my problems for the time being. Definitely looking for a better solution though. Thanks again.
First of all, changing wp-content folder for existing site is a very bad idea. Since files attached to the existing content need to be changed accordingly. If content having significant number of posts or pages, then it will be a tedious thing to sort out. But, don’t be panic there are 3 ways to resolve this.
(1). Since wp-content directory already changed to custom one, then change all links & urls in the content(Posts, Pages etc). For this we have again three ways to resolve.
(A). Export all content using either “Tools>>Export>>All content” or using phpMyAdmin. Now with text editor replace “wp-content” to “wp-xxcontent”(or what ever you have choosen). Now replace the existing content with modified content. Now every thing forks fine.
(B) Using mySQL commands replace “wp-content” to “wp-xxcontent”
(c) Using Velvet Blues Update URLs plugin you can change existing urls to new ones.
(2). Second option to resolve this issue is just removing something from wp-config.php doesn’t work. Using phpMyAdming goto the data base corresponding to the site you have problem with. Find Options table like wp_options or tablename_options. Delete all options names started with “itsec_” (itsec_data, itsec_global . . . upto itsec_tweeks). Also delete .htaccess rules genereated by iThemes Security. It means you have to delete all .htaccess rules between “# BEGIN iThemes Security” and “# END Login Protection”. Now delete iThemes Security Plugin folder from plugins directory and install with fresh copy of the plugin. This time don’t change “wp-content” directory.
(3). If the above two solutions doesn’t work as expected and wordpress installed in its own directory, then culprit is .htaccess file or some thing other. 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.
Hope this will resolve all your concerns.
