Title: [Plugin: WP Super Cache] Preload files
Last modified: August 19, 2016

---

# [Plugin: WP Super Cache] Preload files

 *  [luciatheknitter](https://wordpress.org/support/users/luciatheknitter/)
 * (@luciatheknitter)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/)
 * If I run preload, where do I find the files? (I’m trying to see if it’s working.)

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

 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696166)
 * wp-content/cache/supercache/
 *  Thread Starter [luciatheknitter](https://wordpress.org/support/users/luciatheknitter/)
 * (@luciatheknitter)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696239)
 * Thanks.
    I’d looked in there before since the read me file suggested they would
   be in there. It wasn’t at all what I expected. There are a _few_ files in there—
   maybe 10% of my total posts (if that many.) Some are from 2010, some all the 
   way back to 2007. Not at all what I expected.
 * Isn’t it supposed to go backwards in time, getting all the 2010 first? Then the
   2009 etc?
 *  Thread Starter [luciatheknitter](https://wordpress.org/support/users/luciatheknitter/)
 * (@luciatheknitter)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696240)
 * Also, preload indicates it’s finished. So, only a very few are going to be pre-
   loaded.
 *  [jaykimball](https://wordpress.org/support/users/jaykimball/)
 * (@jaykimball)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696262)
 * Hi Donncha,
 * I recently installed Super Cache, and activated it, and don’t see the Super Cache
   in wp-content/cache/supercache/
 * Also, I don’t see a .htaccess file, except at root level. Your install docs say
   it should be at:
    wp-content/cache/.htaccess
 * In the Tester Tab, when I list all cached files, there is noting in the list.
 * Any thoughts on what I am doing wrong?
 * Also, I get this error after activating, in the Advanced Tab:
    Directly Cached
   Files Warning! /home/content/w/w/w/www8020vision/html/ is writable. Please make
   it readonly after your page is generated as this is a security risk.
 * I am not sure what path that is. It doesn’t make sense for the structure of my
   directory.
 * Thanks for any help you can provide.
 * jay
 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696283)
 * Jay – you’re on shared hosting I presume? You’re seeing a virtual folder, while
   that path above is the real path to where your site lives.
 * Have you tried the debug system? That should tell you a lot about why things 
   aren’t working.
 *  [Inposure](https://wordpress.org/support/users/liangzai/)
 * (@liangzai)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696308)
 * In wp-cache.php, on line 2390, you select all ID from the table `posts` where
   post_status is “publish” when caching in preload mode:
 * `$posts = $wpdb->get_col( "SELECT ID FROM {$wpdb->posts} WHERE post_status = '
   publish' ORDER BY post_date DESC LIMIT $c, 100" );`
 * Thing is, not all items where post_status is “published” are of post_type = “
   post”, but also of post_type = “nav_menu_item”.
 * Caching nav_menu_item will generate a 404 error and slow things down. post_name
   for nav_menu_item is always the same as ID, that is a number.
 * To solve this, WP Super Cache must also check that post_type = “post” in its 
   SQL statement:
 * `$posts = $wpdb->get_col( "SELECT ID FROM {$wpdb->posts} WHERE post_status = '
   publish' AND post_type='post' ORDER BY post_date DESC LIMIT $c, 100" );`
 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696363)
 * liangzai – thanks, I’ve just added this to the development version.
 *  [ewlong1](https://wordpress.org/support/users/ewlong1/)
 * (@ewlong1)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696376)
 * I’ve installed wp super cache – it appears to be working well.
    However, I’m 
   receiving regular emails with the subject line “Preload may have stalled” and
   with the content “Preload has been restarted.” What does this indicate? Is there
   a problem? Thanks in advance for any help on this.
 *  Plugin Author [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * (@donncha)
 * [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696384)
 * Sometimes the preload stops (there are many reasons) but now it continues instead
   of stopping completely.

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

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

 * ![](https://ps.w.org/wp-super-cache/assets/icon-256x256.png?rev=3506220)
 * [WP Super Cache](https://wordpress.org/plugins/wp-super-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-super-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-super-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-super-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-super-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-super-cache/reviews/)

 * 9 replies
 * 5 participants
 * Last reply from: [Donncha O Caoimh (a11n)](https://wordpress.org/support/users/donncha/)
 * Last activity: [15 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-preload-files/#post-1696384)
 * Status: not resolved