WordPress Toolkit Security Measures

[unco]

Hi -

I've had a few instances in which clients have other apps installed in subdirectories in public_html and, after applying security measures, those are no longer accessible. a 404 error is returned. In two cases, the last security measure to be applied is, "Restrict access to files and directories." That one doesn't revert. Other than restoring a backup, is there any way to overcome this issue?

Thanks,
Beth

 

[cPRex]

Hey there! can you get me more specific details? What security measures are being applied and where are you making that change? I would need to test things on my end to ensure I can reproduce this behavior and then see if I can provide you with a workaround.

 

[unco]

Hey! I'm really sorry it took me so long to reply!

This is a WordPress Toolkit problem I'm having. Other than this, WP Toolkit has been a timesaver!

Here's what I'm referring to. This is a screenshot of the option I used. On any site that has a second WordPress site in a subdirectory of public_html, the second site can no longer use permalinks or there's a 404.

I'm not sure what to do about this.

 

[cPRex]

Thanks for the additional details. In order for me to replicate this, can you just confirm the following configuration is the correct way to experience this behavior?

-create a cPanel account
-install WordPress in the main document root of public_html on the domain
-create a subdirectory in public_html
-install another WordPress instance in the subdirectory
-enable the "Restrict access to files and directories" option in the main public_html WordPress
-the secondary WordPress in the subdirectory will start experiencing issues

Does that sound right to you?