Title: [Plugin: WP Super Cache] Directly cached files warning
Last modified: August 19, 2016

---

# [Plugin: WP Super Cache] Directly cached files warning

 *  [epeoples](https://wordpress.org/support/users/epeoples/)
 * (@epeoples)
 * [16 years, 1 month ago](https://wordpress.org/support/topic/plugin-wp-super-cache-directly-cached-files-warning/)
 * I installed the WP SuperCache plug-in today and while configuring noticed the
   following warning message:
 * > Directly Cached Files
   > > Warning! /home2/ericpeop/public_html/epicimagesonline/ is writable. Please
   > > make it readonly after your page is generated as this is a security risk.
   > > 
   > > Add direct page:
   > Directly cached files are files created directly off /home2/ericpeop/public_html/
   > epicimagesonline/ where your blog lives. This feature is only useful if you
   > are expecting a major Digg or Slashdot level of traffic to one post or page.
   > For example: to cache [http://www.epicimagesonline.com/about/](http://www.epicimagesonline.com/about/),
   > you would enter [http://www.epicimagesonline.com/about/](http://www.epicimagesonline.com/about/)
   > or /about/. The cached file will be generated the next time an anonymous user
   > visits that page.
   > Make the textbox blank to remove it from the list of direct pages and delete
   > the cached file.
 * I have no idea what this means. The text below the warning doesn’t seem to address
   the warning at all. What am I supposed to be making read-only and how do I do
   it. Should I do it? What should I do?
 * -ep

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [sandbergs](https://wordpress.org/support/users/sandbergs/)
 * (@sandbergs)
 * [16 years ago](https://wordpress.org/support/topic/plugin-wp-super-cache-directly-cached-files-warning/#post-1501042)
 * the text below relates specifically to creating directly cached files, whereas
   the warning message is a general message about your setup. They are not meant
   to be related.
 * you should be able to solve the warning by logging in with command line and use
   chmod 755 on the epicimages folder.
 *  [yeswap](https://wordpress.org/support/users/yeswap/)
 * (@yeswap)
 * [15 years, 12 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-directly-cached-files-warning/#post-1501105)
 * I’m getting the same message:
 * Warning! /home/boostapp/public_html/ is writable. Please make it readonly after
   your page is generated as this is a security risk.
 * chmod’ing /home/boostapp/public_html/ to 755 did NOT make the message go away
   and neither did chmod 711
 * What permission attribute is WP Super Cache looking for? Everything I’ve ever
   read on security recommends 755 or 711 for web root directories.
 *  [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [15 years, 12 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-directly-cached-files-warning/#post-1501106)
 * That directory is owned by the same user that runs the webserver so ignore the
   warning. It’s not ideal that this is the case but some hosting companies do it
   for convenience.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘[Plugin: WP Super Cache] Directly cached files warning’ is closed to 
new replies.

 * 3 replies
 * 4 participants
 * Last reply from: [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * Last activity: [15 years, 12 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-directly-cached-files-warning/#post-1501106)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics