You are here because the Options All -Indexes tip of sir Macuha did not work out for you? or you figured out that Sir Dexter’s method of making blank index.html and uploading it to your /wp-content/plugins/ or in any folder is just a bit tedious.

At first I tried the method of Marhgil, and yes, I did get a 500 Internal Server Error page.  Frustrated, I quickly reversed it by deleting that one line ” options all - indexes” in my .htaccess.  I also tried Dexter’s blank HTML trick by placing it inside my /wp-content/plugins, the problem is that I have a few… (just a few) blogs and I can not go over them one by one just to upload that blank html file thru ftp.

A Slacker’s Solution

Don’t hit the delete button just yet.

Here is one alternative.  I am not a coder myself and I tried searching for the proper code on how to make your directories not available for public viewing. I managed to get this code from websitesource.com’s tutorials and yes, I have also searched if adding this code will affect the crawling of bots or rankings within search engine results pages, the answer is NO which then will give you now a certain feeling of relief.

The Solution

If the two methods given by the two respected bloggers [Marghil & Dexter] did not suit to your likings, you could try this.

1. open up your .htaccess from cpanel or via ftp.

*If your root directory does not have a .htaccess, you can create one by:

  • opening and saving a blank .txt file with any name.  example: hinlalato.txt
  • upload the file to the root directory, it is common under /www/public_html
  • renaming it now to .htaccess

2. put this code on the very top of the file. it is usually in line #1

IndexIgnore */*

3. Hit Save

4. Now try accessing your /wp-content/plugins

5. Tell me if it worked by commenting below :D

If you have any suggestions, or clarification about this method, please do not hesitate to inform me, I too am a person and MIGHT have missed something.  I am not a coder and this is all based by online research.

One Response to “Hide Those Wordpress Directory Files”

  1. marhgil Says:

    I didn’t know it will cause 500 Internal Server error on some sites. :( I think, this one is a good alternative. Thanks!

Leave a Reply