Moderator
James Huff
(@macmanx)
Volunteer Moderator
wp-content has an empty index.php file in it, which wp-includes doesn’t have.
You should be able to safely copy that same index.php file into wp-includes.
Thanks for the quick response James.
Does that mean if I were to create a new folder under my Domain-name e.g. “domain-name/my-subfolder” and move in an empty index.php file into it that subfolder will also not be visible to Public? I need this to protect some resource files that I would like to keep away from public eyes accessing from a directory/folder level and yet my readers can access via a link that I point to in my WordPress page (hope I’m making sense 😉
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Does that mean if I were to create a new folder under my Domain-name e.g. “domain-name/my-subfolder” and move in an empty index.php file into it that subfolder will also not be visible to Public?
Yes, that is correct. 🙂
If you want to protect all directories by default (without needing an empty index.php file), you could also consider adding this to the .htaccess file in your main directory:
Options -Indexes
Awesome thanks James you’re a star. I’ve been looking for a solution for awhile. I was exploring setting up directories with different chmod code 🙁
