Title: idccomm's Replies | WordPress.org

---

# idccomm

  [  ](https://wordpress.org/support/users/idccomm/)

 *   [Profile](https://wordpress.org/support/users/idccomm/)
 *   [Topics Started](https://wordpress.org/support/users/idccomm/topics/)
 *   [Replies Created](https://wordpress.org/support/users/idccomm/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/idccomm/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/idccomm/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/idccomm/engagements/)
 *   [Favorites](https://wordpress.org/support/users/idccomm/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [wp-includes/css/: No matching DirectoryIndex](https://wordpress.org/support/topic/wp-includes-css-no-matching-directoryindex/)
 *  [idccomm](https://wordpress.org/support/users/idccomm/)
 * (@idccomm)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/wp-includes-css-no-matching-directoryindex/#post-13057889)
 * I also had a similar problem until I figure out it is not a problem… it is actually
   a good thing.
 * You might have in your .htaccess file the line below
    Options –Indexes
 * Which protects folders on your server from being explored simply by using a browser
   as it was some FTP client. This way you protect the WP core files… as well as
   other folders on your server
 * The error log shows you every time that someone is trying to explore a path that
   he shouldn’t. So it’s not an error really…
 * It’s an error only if you actually want people to have access to the path mentioned
   in the error
    -  This reply was modified 5 years, 10 months ago by [idccomm](https://wordpress.org/support/users/idccomm/).

Viewing 1 replies (of 1 total)