WordPress.org

Support

Support » Plugins and Hacks » [Resolved] [Plugin: W3 Total Cache] debugging w3tc cache preload / prime

[Resolved] [Plugin: W3 Total Cache] debugging w3tc cache preload / prime

  • petskratt
    Member

    @petskratt

    are there any suggestions for debugging W3TC “cache preload” functionality – it works on my Mediatemple installs but not on another (rather custom) hosting…

    * I have enabled “Automatically prime the page cache” under Page Cache’s “Cache Preload”
    * normal page cache works when pages are visited, directory structure is created and files served
    * but unvisited pages are not built in batches according to preload settings

    http://wordpress.org/extend/plugins/w3-total-cache/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Frederick Townes
    Member

    @fredericktownes

    Do you have XML site maps on those other sites?

    Hubert Nguyen
    Participant

    @hubertnguyen

    Frederick, is it fair to say that the preload feature “bakes” the .php files after they’ve been processed by MySQL and WordPress? I wanted to ask you:

    1- are they baked in PHP or in .html (like WP SC)? I’d like to know if I can process PHP code dynamically

    2- are those preloaded pages deleted/updated when I modify a post? (I don’t use WP’s commenting system)

    Plugin Author Frederick Townes
    Member

    @fredericktownes

    I don’t understand the question, cached files expire at the specified age or when comments or modifications occur. Fragment caching should be used for pages that are dynamic, pre-loading/priming has no affect regardless of whether fragment caching is used or not.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Resolved] [Plugin: W3 Total Cache] debugging w3tc cache preload / prime’ is closed to new replies.